True, but sadly i still will have xp11 installed for some good jewels that will never be migrated like the A300/310 and some few others… But yeah, the rain effects, clouds, light and atc, spoil all the experience that makes hard to return to xp11.
A couple of issues that may complicate my ability to forward a useful comparison. 1) with ASW locked at an FPS of 30, that’s all I will ever be able to achieve. To me, an old-fashioned gamer who grew up with TRS80s and Atari 800s, 30 FPS is rockin’. But for most, it’s probably not enough. 2) The FPS counter doesn’t work in VR.
I tried again with ASW in Auto and the flight was very stuttery, especially as I passed Linden and Newark. So limiting the framerate probably explains why I have less reason for complaint. It’s when the sim is free to seek the best performance possible that stutters become noticeable. ASW and “Clock30” lock it at 30 FPS or less which stabilize performance changes which the player perceives as stutters.
pretty good test run I would say. no worries, we all have our own setups we wont change that easily.
I did my test run yesterday around the same time you did yours
agree on the FPS lock. it definitely helps with micro-stutters. what I experienced was small micro-freeze right after takeoff. its like micro-stutter but exploited for longer time period and happening not regularly.
tookoff from 39N and set the heading circa 040 and landed at 47N. didnt get too far.
XP12 in R22 (+ X-America osm data for better placement of buildings and trees)
all maxed, 2xAA, 2xAF, in 4K pancake, I saw 35-40FPS, with min 32FPS during landing.
no FPS lock, so micro-stutters were present at occasional FPS drops which were quite high -4FPS what is noticeable.
XP11 in Cicare8 (+ X-America osm data for better placement of buildings and trees; + Global Forests)
all maxed, 2xAA, 2xAF, in 4K pancake, I saw 40-45FPS, with min 37FPS during landing.
no FPS lock, no micro-stutters were present as FPS drops were quite low -1FPS what isnt noticeable.
at this point we could say that thats a great success! but …
then I moved to Bora Bora. not many buildings, not many trees. small islands in the middle of ocean. one would expect significant boost in performance in both versions. not so much.
XP12 went from mentioned circa 40FPS to 60FPS
XP11 went from circa 45FPS to 90FPS
thats 50% increase and 100% increase.
at this point I would blame XP12 new water and waves. missing slider in settings to turn it down to see the effect on performance. Talking settings and FPS lock, Asobo did better job here. e.g. vsync in MSFS can be tuned for % of the native refresh rate so basically I can set easily ingame FPS lock at 30 / 60 / 90 / 120 FPS on a 120Hz panel without manipulating refresh rate.
what else I would blame on LR is lack of new development on scenery. its basically XP11 scenery ported over with slightly better textures. mesh is lacking, osm data for buildings and trees are lacking, etc.
results : shelving XP12, sticking with XP11 (despite washed out picture) and will follow development in regards to scenery and performance tuning.
in general I think XP is very good in two things - 1) flying in jets high in the sky and falling only to nice airports 2) flying anything else down low from some particular nice base (like Bora Bora, Horta, Casco Cove, Catalina, etc.) and flying just around the chimney.
no. 2) is my happy place (with high fps)
I just cant watch 30fps/hz on my panel (even locked). already in win desktop I can see my mouse cursor has jaggy movement. thats ‘standard mode’. ‘game mode’ on this panel can run only 100 or 120Hz, not lower.
FYI:
I flew the R22 around 39N in VR, stock XP12 (beta 5?) around 700 feet at noon with scattered cloud layer starting at 2000ft and Nvidia drivers 522. Average FPS was 40 with no stutters. I can’t remember what the X-Plane graphical settings are. I am running an AMD 5800X with an Nvidia 3080Ti.
Clouds too, I’d imagine. Agreed on scenery. That may well be what kills X-Plane. Austin promised us no real changes and yet we held out hope that he was holding back. He wasn’t! I don’t mind it really except for the horrible building placement. My phone in “Car Play” shows each individual house as a roughly correctly shaped block on the 3D map as I drive. OpenStreetMaps, the source for X-Plane’s autogen, doesn’t depict structures, just general structure density. Your screenshot of Princeton looks exactly right. But when you takeoff to the east, you immediately fly over a shopping center. In X-Plane, it’s just that same old strip of single-family ranch homes. 3 miles to the SW is the lovely Princeton campus. In the sim, nada.
as the saying goes, it is what it is … yes, I just hoped for slightly more detail coming from some more recent data sources
btw wondering about your 30fps. @Fridge 's results seems to me more in line with the gpu. didnt you upgrade recently also?
will give it one more go with the CitationX to have a close look at the clouds. realized I saw them from below only up until now.
Beta 8
- XPD-13113 – Still having “Approach has gone backwards” and VFR approaches going missed.
- XPD-13020 – Legacy Dataref CG Z Maps to Wrong Unit.
- XPD-12077 – Bug report: light_attenuation dataref alway 1.0.
- XPD-13228 – Art: Pilots for A330 and 737.
- XPD-13223 – Update Scenery Gateway missing runway autoreporter URL.
- XPD-13218 – Handle contact point fails a dev assert when checking for collisions.
- XPD-13170 – sim/graphics/animation/carrier_catapult_station_rat not working for XCAR3 and XCAR4.
- XPD-13152 – Hiding the ground-ops window in VR also hides the ATC window.
- XPD-13149 – XPLMSaveDataFile / XPLMLoadDataFile – save/load inccorect data.
- XPD-13125 – Erroneous dataref values in sim/world/boat/{x,z}_mtr[0,1].
- XPD-13102 – Potential crash after departure.
- XPD-13093 – Hold-short messages may refer to the wrong end of active runways to cross.
- XPD-13092 – MIssing sim/world/boat/carrier_catshot_status?
- XPD-13091 – set radio nav freq by dataref does not work correctly.
- XPD-13089 – sim/ice/anti_ice_toggle command is not working.
- XPD-13077 – Wings dont droop under fuel load.
- XPD-13071 – CTD when using CDU815 in custom A/C in PM.
- XPD-12831 – Datarefs overwritten during merge.
- XPD-12797 – Request to allow VFR landing after a zone transit.
- XPD-11427 – Bug report: XPLMCanWriteDataRef always returns true for DataRefs.txt.
- XPD-11400 – Horizon tilts when panning tower view.
- XPD-13214 – From Bug Report: Panel maker interface for 3D panel shifted and unreadable.
- XPD-13172 – Citation X has brakes still set to hydraulic system B, should be A.
- XPD-13154 – Zone transit should use actual airspace boundary if it’s not ridiculously large.
- XPD-13153 – IFR clearance should include a squawk code even for relayed clearance.
- XPD-13138 – Unable to change aircraft basic information if departure ICAO is populated.
- XPD-13114 – LSO is calling “drop your hook” for aircraft with no tailhook.
- XPD-13095 – Taxiway names with spaces were not loaded correctly.
- XPD-12087 – Request for a dataref that shows the state of the UI selected scaling.
- XPD-13217 – Pronounce name of Ethiopia’s Bole airport (HAAB) correctly.
- XPD-13141 – F14 F-14 Tomcat Right and Left Engine Fuel Shutoff Handle INOP.
- XPD-13132 – Ground Attitude in Plane Maker acts crazy.
- XPD-13122 – Slow speed taxing of the MD82 excessively rolls the aircraft.
did additional test run (before tha latest beta8).
this time resolution 2K, settings maxed out except SSAO - none (I think I am not really fan of these post effects).
Bora Bora NTTB
performance around 90 what is finally acceptable for me
all is nice and fun …
… until one see things like these
but flight modeling is improved in XP12. even the default C172 feels much better in XP12 than XP11. so there is that.
The eVTOL is quite nice, actually. Funny thing, in my real flying I switch controls all the time. Some days I fly the 767 from the left seat, other days from the right. At home I fly the Pitts with my right hand and same with the Robinsons. But I cannot seem to be able to eliminate my stick/collective confusion with the Beta. Changing the VR config so that I fly from the right seat did the trick. It’s very pleasant to fly and the transition from forward to hovering flight is interesting. I do wish that the charge lasted more than 10 minutes (and that it could be recharged).
Also, there is a key command to recharge the batteries (search “recharge…”). The most important piece of information in the machine is the voltmeter. Appropriately, it’s a teensy-tiny little yellow value on the bottom of the right display titled “v”.
oh, really? was naively thinking it has better performance
but there is solution
https://store.x-plane.org/VSKYLABS-‘Contaventus’-Renewable-Energy-Glider-Project-20_p_651.html
Beta 9 Released
Beta 9
- XPD-12924 – Crashes when enabling FSR with mis-matched monitor aspect ratios.
- XPD-13263 – Weight and balance system acting weird after resaving aircraft with latest planemaker (SR22 example).
- XPD-13235 – RV10 visible polygons in internal glass.
- XPD-13266 – New Landmarks package: Portland.
- XPD-13262 – Updated Global Airports.
- XPD-13249 – New assets for legacy airport scenery objects.
- XPD-13239 – (Light) aircraft pitch down unduly at the moment of touchdown.
- XPD-13180 – F-14 Tomcat Missing Livery Preview (VF31 AJ105 BuNo 159619).
- XPD-13148 – Regression in XPLMPlaceUserAtLocation() function with gear position.
- XPD-13046 – Move crashpad handler executables to the proper “shipping” locations.
- XPD-13045 – Implement GUI for new crashpad handler.
- XPD-12812 – UI: No visual indication of the splitter bar in the ATC dialog.
- XPD-13238 – Expose rain debug utility to developers.
- XPD-13178 – Lancair Evolution Particle Separator has no effect.
- XPD-12824 – strange surging effect of rainstreaks on windows (starts-stops-starts-stops…).
- XPD-12749 – Ground handling speech doesn’t have signal processing.
- XPD-13143 – Cirrus Vision SF50 Landing lights not visible during the day.
beta 13 is up. I am out of town but the crowd at dot org are largely impressed with the improvement in performance.
saw it, didnt have time to update.
tested only old MLADG L29 inside v12. didnt perform well.
I saw a report it’s breaking Orbx sceneries, so I want to do a bit more digging first.
I"m wondering if XPlane 12 can use more then 1 CPU core. Is there native support for multi-core CPUs nowadays?! I remember that developer in past mentioned support for multi-core CPUs in new version.
Good question. But I think performance issues are something else. X-plane runs better than DCS and MSFS for me, both in VR. Thats with a 5yo CPU and a 3080. There is some combination of hardware that’s throwing it off for some users. If it were is simple as core utilization, I think the problems would be universal.
just checked resource monitor and XP12 definitely utilizes more than single core