November 9, 20169 yr With 3.4.9, I had a dramatic rise in VAS usage over 3.3.5, and regular OOMs during VFR GA flights with conservative settings. There were no improvements with a client only install of 3.4.14, so I rolled back with a full install of 3.3. And without being able to use my old Orbx installers, OUCH!! But 3.3.5 was stable and I never OOM'ed with my settings, so guess I'll hope for an improvement in 3.5. Same here Regards, Chris -- PC: Intel 13900K, Gigabyte Geforce RTX 4090, 64GB Fury Beast DDR5 RAM; Display: Varjo Aero VR
November 9, 20169 yr Same here Upon initial re-testing of 3.3.5, VAS is stable so far. Consistent with my first 3.3.5 install. <p>Dassault Falcon, Lear, Embraer and Challenger and Cessna Mechanic.Broadcasting live from former Soviet Missile Silo.Rhys Legge
November 9, 20169 yr You're paying for a license, not installation media... Tell that to LM, if you bought an earlier release but could not be bothered to back it up then it's gone. P3D is a perpetual beta, there will be issues along the way, to not back up installers seems crazy to me.
November 9, 20169 yr Staying with my ever stable 3.3.5. Will not upgrade for some time me thinks. Eric
November 9, 20169 yr Staying with my ever stable 3.3.5. Will not upgrade for some time me thinks. Ditto.
November 9, 20169 yr Fixed a lot on my version of P3d V.3.4:- IStation via Wide FS 7 now works correctly, which should imply FSUIPC ok. Airbus Control problem now cured on my setup. Much more inherent stability in the program. Only casualty so far Active Sky 2016 and FS Passengers - For Active Sky it is an ASConnect Issue. So far for me its positive I wait for an Active Sky update
November 9, 20169 yr For those that rolled back to 3.3.5 (vas issues).. did you just uninstall the newer client/content and reinstall the older (in my case i updated both client and content), any issues? 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
November 9, 20169 yr Sorry, I should have clarified. I already migrated all my orbx purchases to ftx central v3 and orbx direct. Once you do that you must download, thru ftx central v3, all your products again, but only once, as you can create local backups during install to reinstall from later if needed. But all the FSS installers cease to work once you migrate. Me too, and loving it. Still use both but xp is seeing increasingly more usage as the days go by. Not true...the old FFS installer work, but ONLY if you still have the registry entries..and did not reinstall your O.S. system. They work, but if you have to verify the license, via the 'from the net'... instead of an already-installed on your O.S....then you are done.
November 9, 20169 yr Not True , as you say, I reinstalled win10 and then using FSS reinstalled some ORBX , it ask for the date number and key and unwraps OK.. no problem, you must not transfer anything for this to work (as I have not). Jorge
November 9, 20169 yr Ditto. Staying with my ever stable 3.3.5. Will not upgrade for some time me thinks. Me too! Hamilton Müller
November 9, 20169 yr Not True , as you say, I reinstalled win10 and then using FSS reinstalled some ORBX , it ask for the date number and key and unwraps OK.. no problem, you must not transfer anything for this to work (as I have not). Jorge That you haven't transferred your purchased products is exactly the reason why the original installers still work.
November 9, 20169 yr and what did it fix? be more precise I have lived with problems since the early days of P3d - version 3 was a start of some kind of light at the end of the tunnel - its not perfect but then nothing is. As to your comment fixed implies that these issues were non functional no matter what corrections were tried before. Now upon update of the client they work as the manuals say they should. The change of state from broken to fixed is precise enough when no other action other than the update occurred. Myself I am likely to believe that the hotfix was the causative agent - of course there is always a miracle I suppose
November 10, 20169 yr For those that rolled back to 3.3.5 (vas issues).. did you just uninstall the newer client/content and reinstall the older (in my case i updated both client and content), any issues? Just uninstall the newer client, and install the older. Reactivation required. You can leave content and scenery with the newer version. Works. Regards, Chris -- PC: Intel 13900K, Gigabyte Geforce RTX 4090, 64GB Fury Beast DDR5 RAM; Display: Varjo Aero VR
November 10, 20169 yr Cargostorm, on 10 Nov 2016 - 06:43 AM, said: Just uninstall the newer client, and install the older. Reactivation required. You can leave content and scenery with the newer version. Works. This is interesting. How about AS2016, PMDG, FSUIPC? Do I need to roll them back as well? Thanks, Dirk.
Archived
This topic is now archived and is closed to further replies.