October 3, 20169 yr I'll try to run the test tomorrow and have some numbers to add. CASE: Fractal Terra Silver CPU: AMD R5 7800X3D 5.0Ghz RAM: 32GB DDR5 6000 GPU: nVidia RTX 4070 Ti SUPER · SSDs: Samsung 990 PRO 2TB M.2 PCIe · PNY XLR8 CS3040 2TB M.2 PCIe · VIDEO: LG-32GK650F QHD 32" 144Hz FREE/G-SYNC · MISC: Thrustmaster TCA Airbus Joystick + Throttle Quadrant · MSFS2024 · Windows 11
October 4, 20169 yr Here my findings at stand 5 at ESSA in the NGX following the steps outlined in post #18. 1405952 with OP set to 1 (FPS 55) 1426304 with OP set to 0 (FPS 47) As you can see an improvement looking at VAS but not by much where the FPS instead dropped by a more significant amount of 8 FPS. One thing I was thinking. Could the change in VAS behavior looking at 3.3 vs 3.4 has anything to do with the technique P3D used to release VAS memory during a flight? Reason I came to think of this is I don't really see that much of a difference in VAS when just checking a specific situation like this one standing at a gate after starting P3D. The difference I've seen seems to be more after doing some flying where P3D both loaded the scenery at my origin as well as loading different scenery and weather along the flight and then finally loading the scenery at my destination. Would have been interesting to do this same comparison between 3.3 and 3.4 after doing a full flight in the same conditions. Edited October 4, 20169 yr by WebMaximus
October 4, 20169 yr Hope that there's a hotfix coming out for this problem. Angus Rowlands: i7 8700 RTX Asus Strix 2080, 16 GB RAM
October 4, 20169 yr What problem? So far we seem to see a trade for a relatively small amount of VAS for a significant performance improvement. That doesn't strike me as unreasonable. [email protected] - ROG Strix Z790-E - 2X16Gb G.Skill Trident DDR5 6400 CL32 - MSI RTX 4090 Suprim X - WD SN850X 2 TB M.2 - XPG S70 Blade 2 TB M.2 - MSI A1000G PCIE5 1000 W 80+ Gold PSU - Liam Li 011 Dynamic Razer case - 58" Panasonic TC-58AX800U 4K - Pico 4 VR HMD - WinWing HOTAS Orion2 MAX - ProFlight Pedals - TrackIR 5 - W11 Pro (Passmark:12574, CPU:63110-Single:4785, GPU:50688)
October 4, 20169 yr Optimize part=0 : Flytampa EKCH VAS= 1541804 FPS= 47 Aircraft PMDG 737-700 Optimize part=1 : Flytampa EKCH VAS= 1529040 FPS= 57 Aircraft PMDG 737-700 André
October 4, 20169 yr Optimize part=0 : Flytampa EKCH VAS= 1541804 FPS= 47 Aircraft PMDG 737-700 Optimize part=1 : Flytampa EKCH VAS= 1529040 FPS= 57 Aircraft PMDG 737-700 Very similar to my findings both looking at VAS and FPS.
October 4, 20169 yr The tradeoff between FPS and VAS for me is leaning towards leaving OP=1 on. The sim takes a big performance hit without it. FSUIPC will at least allow me to pick up where I left off in case of an OOM. Let me guess.... you want 64bit. Josh Daniels-Johannson
October 4, 20169 yr Ditto ;-) - PC Hardware: AMD Ryzen 9 9950X3D // Asus ROG Crosshair X870E HERO // 2x32Gb Corsair Dominator Titanium DDR5 6000MT/s CL30 // ASUS ROG Strix GeForce RTX 4090 OC Edition // 4Tb Corsair NVMe M.2 MP600 // Corsair 1600W PSU Samsung Odyssey Arc 55" curved 165 Hz monitor. - Simulator Hardware: VIRPIL Constellation Alpha Prime + VIRPIL VPC Universal Control Panel - #3 + MOZA AY210 Force Feedback Yoke + WINWING URSA MINOR 32 Throttle & PAC Metal + WINWING SKYWALKER Metal Rudder Pedals + WINWING Airbus FCU & EFIS + WINWING Boeing 3N PAP + WINWING MCDU-32 + WINWING PFP-4 + WINWING PFP 3-N + WINWING PFP-7.
October 4, 20169 yr This entire discussion shows that no matter what they say, in the end it comes down to the simple fact, that with current add-ons on the market and used in combination with each other, the only definite solution is to develop a 64-bit Platform. As much as P3D has improved with releasing VAS, something FSX never did, it is still vulnerable to the memory overload. I really look forward to a time, when VAS discussions will no longer happen.
October 4, 20169 yr This entire discussion shows that no matter what they say, in the end it comes down to the simple fact, that with current add-ons on the market and used in combination with each other, the only definite solution is to develop a 64-bit Platform. As much as P3D has improved with releasing VAS, something FSX never did, it is still vulnerable to the memory overload. I really look forward to a time, when VAS discussions will no longer happen. I am with you Karsten (btw. cool Name ) But i promise you the next discussion flood after having 64bit platform with "what scenery is 64bit compatible and what tweaking can be done to make it compatible" Not sure if that will be less painful discussion. Cheers, Carsten Carsten U
October 4, 20169 yr i ve just started a flight between nantes LFRS and athenes LGAV with pmdg 737, with a was @ 1250mb, now and after 20minutes of flight vas is @951 mb optimize part =0, shader are rebuild Frédéric Giraud
October 4, 20169 yr i ve just started a flight between nantes LFRS and athenes LGAV with pmdg 737, with a was @ 1250mb, now and after 20minutes of flight vas is @951 mb optimize part =0, shader are rebuild And what was vas usage with optimize parts=1 at that stage of the flight ? Carsten U
October 4, 20169 yr since version 3.4 is out, the max time spend to fly is 1H45, and when i land vas show 700mb with OP=1 i am actually above the sea to athenes 2H15 flight, and vas is 989mb always with OP=0 Frédéric Giraud
October 4, 20169 yr Does anyone happen to have a good saved flight plan they can link for download (something with gps autopilot path laid out for testing this) / and/or recommended aircraft to test? That way each test can be exactly the same for the most part? I assume most are using fsuipc with 024C and Type =32 sent to title window or console window perhaps (or log file)? Asus Strix z790-e; 1000 watt evga SuperNova Plat; 14900k AC_LL 0.55 adp -0.050 253/253/355 CEPoff (CB-1pass 39200 80c, msfs peak 92,avg 60-78c, astrorender 95c,room76F); 64GB(dual 32) cl32 6400 at 6400 xmpII F5-6400J3239G32GX2-TZ5RK, Asus Ryuo III 360mm; Thermaltake v51 Case; Gigabyte 4090 OC; VR-Crystal; Dofreality H6; Astrosite
Archived
This topic is now archived and is closed to further replies.