Rogen

Ok np. Cheers https://www.avsim.com/forums/topic/617667-orbx-terra-flora-v2-updated/

Sure... from Orbx, you have to buy them of course. Then configure the packages and adjust the Prepar3D.cfg to increase the density of vegetation. Cheers

I'm pretty sure if you're running v5+those shoreline waves are disabled/removed as a default. I still run shoreline waves though, but I use the "Global_Orbx_Wave_Effects" package rather than the default FSX style. Global_Orbx_Wave_Effects is a freeware package from Orbx originally designed for P3D v4, the package still does function on P3D 5+, however the changes to effects structures (in particular to transparency) means a person must manually edit the effects files on a trial and error basis to cater for the transparency shift, (because LM didn't document a "How To" make suitable compatibility changes that I'm aware of). Anyway, they do look pretty fine as shown in the vid below. There are also a few other shoreline wave packages created by other devs as well but the Orbx crew's package is the nicest overall.

I wouldn't say the pics look better than MSFS overall, that said P3D is a pretty open platform and with the right amount of programing & configuration effort P3d can look pretty fine IMHO. The main issue I see is people shy away from configuration effort preferring to run in the default config because it's not their "thing" to adjust configurations to suit. Cannot really blame consumer level users though, LM never did make it easy to understand. Even the Prepar3D.cfg is not well documented, the platform is basically LM's product they build and configure for their direct customers (who spend $$$ in the multi millions), leaving everyone else pretty much on their own. Cheers

I would have thought such discussion on tress would have been long put to bed given the trees representation in P3D was much the same as FSX unless "Dynamic 3D Autogen Vegetation" was enabled which turned on Speed Trees for dynamic vegetation movements (e.g. with the wind) when low to the ground. Admittedly one of the worst things is the poor colour palettes LM had chosen (and subsequently ignored), hence the quite unrealistic lime green. I originally used a free tree package that came as part of ALeclercq Creations Terra Emergence Project given there wasn't much else at the time (FSX days), better than the default and great for the cost. Then came Orbx HD trees which were designed to suit Orbx scenery and included upgrades of several tree species only present in some Orbx scenery packages. Then came Terra Flora, followed by Terra Flora v2... Terra Flora v2 is the best looking, however it has a weird xml configuration enablement system when installed as an addon that's caused me some issues at times, plus I discovered the package was missing tree textures - since resolved by Orbx. In the end I built hybrid packages consisting of Terra Flora v2 & Orbx HD Trees with just the alternate vegetation components to suit Orbx, along with config adjustments for coverage changes. Note: A tree package will update the default trees everywhere they are used, although some alternate scenery packages include their own specific trees which likely won't be replaced by the tree package, indeed you can notice such in non-Orbx New Zealand packages and also in many Orbx sceneries where selected Orbx trees are animated to move with the breeze. Here's a few pics of the trees and vegetation as I've configured, should give a good idea of how it all looks.

Hi Ray, For myself it's more about getting Windows setup to the sort of functionality I'm after, and yeah it's a little more on the tech side but then again I've spent over 20 years in I.T. and software development and the tech side is what I lean to. The tool does have help options and a person can always Google a particular item to gain a fuller understanding of said item, plus item changes are typically easily reversed. For instance I don't use Edge, but I do know some web components are installed along with Edge and maybe needed by other apps, so I don't want to uninstall Edge, but I also don't want it starting threads automatically behind the scenes unless I've commanded, so we can disable Start Boost which is just a fancy name for auto run in the background and thus prevent Edge running threads even when you've not opened Edge. Edge also has a settings option of "Continue running background extensions and apps when Edge is closed" which I set to off, as when I close Edge I expect it to also close any child ops it may have started. I also don't buy into the so called A.I. "Features" MS is foisting upon people and thus I've removed said A.I. from Windows. If you look into the corporate logic of MS you should be able to see they don't really care for the users of Windows per-say... Users are just a temp hindrance to be turned to the path of subscription income, corporate control and as much A.I. slop as MS can pump into Windows, their apps and Azure server systems... all while shoving advertising and selling your data to third parties based on your workstation's TPM I.D. value and subsequent history profile. and no I don't have a tinfoil hat 😁 Cheers

I noticed a Steam user also bringing such an issue up in the FSX-SE forums. I guess Win11 is a magnet for introducing more new and exciting bugs... And now with built in AI-Slop 😉 I recently found a tool to assist with cleaning up Windows, people might find it of use. https://github.com/builtbybel/Winslopr Cheers

What does this mean ? Cheers

Check your inbox / spam folders. Cheers

Actually it sounds more like Reshade rather than Envshade. Envshade modifies the actual shaders of P3D itself i.e. those shader files that exist in the folder \Lockheed Martin\Prepar3D v(number)\ShadersHLSL\ Where as Reshade and this NVidia option exist outside of the application (P3D in the discussed instance). In actuality I've been using Reshade for years in P3D as well as in the various games I choose to play on and off alongside P3D. A big advantage of Reshade is that it runs outside of P3D and you can pop open the interface and modify the look and feel on the fly so to speak 😉 , also a big plus is that Reshade uses very few resources (assuming you're not trying to do anything over the top). Reshade has a huge number of shader options, including one called Vibrance which does much the same as the NVidia version, and options like tiltshift as well as many others, you can also define custom screen shot configs. I typically use ~5 Reshaders with P3D v4.5 to manage the following. colourTemp (how warm or cold the graphics are) depthshading (yes, even though P3D v4/5 has no depth shading built in, it is possible to add a degree of such) lumaShapening (sharpens just the luma component) debanding (debands, used mostly for the sky) autoExposure (dynamically adjusting the exposure - how bright P3D looks) Fun fact... there is an auto exposure option built into the P3D v4.5 shaders just like in v5, however it is not enabled, I gather the dev crew didn't complete it fully within their release timelines. The below screen pic shows a very small list of only the shaders I am currently trialing/working with, in reality there are hundreds to choose from. Cheers Reshade Tiltshift pics.

Additionally there are some nice fixes for the Milviz Beaver, especially if you're running P3D v4.5.

Whilst I don't know anything about "Beam" itself, I did in a quick google lookup and read Beam used OpenTrack as a provider for its functionality. I do have OpenTrack installed (version 2023.3.0) and it does work fine. This morning I updated OpenTrack to version 2026.1.0 and straight away it refused to load simconnect selections with the error of "not a valid Win32 app %1". Rolled back to 2023.3.0 and all is functional again. You can download the versions of OpenTrack from the below GitHub link. https://github.com/opentrack/opentrack/releases I note there is an issue raised on OpenTrack's Github issue tracker regarding simconnect issues, you might want to create a GitHub issue ticket containing your own experience and also follow up with the Beam crew. Cheers

Hi @JonP01, You don't mention the GFX card model or the NVidia driver version in use, however seeing as NVidia Smooth Motion was introduced originally for 5000 series cards and has been backported for 4000 series cards one would assume either a 5000 or 4000 series. Some general info for those to whom the term "Smooth Motion" is an item of unfamiliarity, essentially its NVidia's version of universal Frame Generation built into their driver package. https://www.nvidia.com/en-au/geforce/news/nvidia-app-global-dlss-overrides-rtx-40-series-smooth-motion/ Going by redit denizens, NVidia Smooth motion has its issues, which will no doubt either be gradually overcome or SM will be dropped for some other technology that will eventually replace it. Have you trialed Lossless Scaling at all ? Given my GPU is a 3080ti I've no options for trialing smooth motion, however I've found LS works fine for myself where I use it not only on P3D but also many games. 2 x clips, a short panning clip of LS in action and a longer flying clip, top left is the LS frame generation enhanced frame rate and bottom right is the fps P3D is locked at. Cheers

Perhaps having a read through of this thread below will help. Both yourself and the thread author have the common denominator of a new Windows 11 PC. Cheers

Ok, that looks a good spec machine, I do know P3D is having issues with the display of certain special effects and 5000 series GFX cards, you can read about it at the below link. https://www.prepar3d.com/forum/viewtopic.php?t=155789 Apparently LM have notified Nvidia and Nvidia are working on a resolution, that said there are many other bugs and inconsistencies in the 5000 series GFX card drivers affecting many different games, hopefully the drivers will mature and the majority of issues will be resolved sooner rather than later. Note that although FSX is not P3D, the two sims are closely related and do have a high degree of inter-functionality of addins, do you see any of the issues reported at the forum link ? The 4 GB patch would have set the Large Address Aware flag in the fsx.exe file headers, you can use Wumpbin to confirm and I would expect to see "Application can handle large (>2GB) addresses" in the file headers. https://www.benf.org/other/wumpbin/index.html Is the memory issue an actual OOM generated by FSX ? i.e. does a warning dialog open ? Or does it just crash outright ? You might want to run a VAS monitoring tool, the links previously provided and Google should help you find a suitable tool, with a monitoring tool you can see when VAS is approaching limits and with the tool help identify what is using VAS to the point of running out. Also the Windows Event Viewer will likely help as crash events are typically recorded in the Windows logs, use Google if needing help to understand the use of the Windows Event Viewer. A process of elimination could be the ultimate troubleshooting path to follow, time consuming though... i.e. disable addins and test, then add each addin back one at a time and retest, I typically have a saved scenario for such testing purposes so as to replicate the same flying scenario each test. I do recall not having OOMs with just default FSX and it wasn't until I'd began chocking up on addins (especially scenery) that I began to hit OOMs. Unfortunately I'm unable to access the Bible link (login required), but if you're first installing FSX via its disks then all should be properly set up and if the laptop self diagnostics don't record any issue then all should be good in that regard. I assume you've the HIGHMEMFIX=1 under the [GRAPHICS] heading in the fsx.cfg ? The only other thing I can think of is to trial an alternate virtual memory configuration, like the one discussed at the below link. https://steamcommunity.com/app/314160/discussions/0/787664259085542515/#c787664386892244402 Of course VAS OOMs are always going to be an issue with 32bit programs, that's why I went P3D x64 as soon as it was practical. Cheers

I circle back to the two original questions asked, being... What's your new hardware specs ? Also what version of FSX is being used ? The Erazer Major comes in several different hardware spec varieties, which one is it? And what is the version of FSX? Circling back to FSX being a 32 bit program, the disk version of FSX will only be able to access 2 GB of ram no matter how much ram your new machine has. You can however patch the fsx.exe to set what is known as the Large Address Aware flag to enable FSX to use the full 4 GB of ram a 32 bit program can access, the links previously provided do contain further info. You can download a 4 GB patcher from https://ntcore.com/ noting there are other patching tools available, up to yourself really. Note FSX-SE (The Steam edition) by default has the 4 GB patch applied (as well as a collection of fixes the disk version doesn't contain), hence the question of what version of FSX are you using? because if you're already using FSX-SE, then there would likely be something else going on. You're probably also experiencing the same issue with rFactor which is 32 bit, as compared to rFactor 2 which is 64 bit, if it's the 32 bit version try the 4 GB patcher on that too and see if it helps. Could also be some weird hardware thing going on, bad ram for example, laptops will usually have a diagnostics option on boot up, might be worth investigating. Cheers PS. I just realised you've mentioned coping game files from one machine to the other, does this mean you're not actually running the FSX installer program?

Got a link to the aircraft ? Cheers

Actually I'd steer more to an Ant's Aeroplane rather then Carenado, given applying mods and fixes to my own Carenado aircraft has shown me how much they reuse code and variables and manage to introduce many bugs and problems that are never fixed (hence mods and fixes). Where as Ant's Aeroplanes had taken on feedback and resolved issues resulting in planes that are very mature coding wise. Anyway, the aircraft look good, fly well and quite easily, do require a minimum level of maintenance and have in-sim flight manuals and configuration options, yeah the range of aircraft is small but those he does have are pretty good and cost $10.95 to 18.25 USD or a little more from Just Flight or Simmarket, you can even download a demo versions if you'd like and yeah I'm giving him a plug because not only are the planes pretty great, I'm amazed he can do them for the price and he resolved some very specific problems I managed to identify and provide feedback on back when I first bought them. I particularly like the Sierra LSA, the Tiger Moth Pro, the Winjeel (a unique Australian trainer) and the Trojan T28 (a warplane). Here's a few pics of the Sierra LSA, these are taken @ Milford Sound NZ and Quinton Lodge NZ. Configuration options page, the GPS says RXP and default 500 series as I've customised the panel.cfgs specifically for the RXP GTN 750. Maintenance options, the engine will tend to die unexpectedly if not maintained, not quite at the A2A level of maintenance needs but certainly more than a Carenado. Canopy rain effects. Cheers

I second the A2A series. The A2A C182 was the first third party aircraft I purchased (back in the FSX days) and it's even better in P3D. Their Comanche is also pretty good. And I like the Ant's Aeroplane collection as they have wear and tear and many features that are amazing for the price. https://www.antsairplanes.com/ I especially like the Sierra, the Trojan and the Tigermoth. Also don't go past the various freebee collections like Blackbird and Realair. And the Vertx Diamond DA62 is very nice and even has wing flex. That's all from me, cheers 🙂

What's your new hardware specs ? Also what version of FSX is being used ? FSX is a 32 bit program meaning it has built in memory usage limits no matter how much ram your hardware has installed, personally I've used P3D v4.5 and I migrated my FSX SE collection over to that P3D version and have been able to fully load all my scenery and aircraft without any OOMs as P3D 4.5 is 64bit. I was even able to migrate a collection of FSX's default aircraft. Here's the FSX default C172 migrated over to P3D x64 But back to FSX... Typically the memory limits for the disk versions of FSX is 2 GB, or 4 GB if the Large Address Aware flag is set, noting the Steam FSX release is the only version I'm aware of that does have the LAA flag set by default. Here's some links to further OOM info: https://support.precisionmanuals.com/kb/a108/vas-management-stopping-out-of-memory-oom-errors.aspx https://steamcommunity.com/app/314160/discussions/1/4149455258718448414 https://steamcommunity.com/app/314160/discussions/0/1291817208500306625/ Something else you might want to look at is JJ FSX's guide on "Install FSX on Windows 11 SUCCESSFULLY the first try...or the second if your already in trouble." available at the below link. https://steamcommunity.com/id/JJFSX/myworkshopfiles/?section=guides&appid=314160 I also remember people in the Steam discussions talking about a customised Windows Virtual Memory configuration giving good results for OOM issues, you'd have to search for those topics yourself though... Cheers 🙂 hope the above helps and let us know how you get on.

Yes, Carenado does have the C172RG CUTLASS II FSX/P3D and while it's an OK plane, it's not anything to write home about... it's also not anything like the A2A 172... And while Carenado aircraft do look pretty good, they tend to have many bugs and be quite bland overall, still... there is a sale on atm... One thing many Carenado aircraft do have is modding opportunities, take a look in the AVSIM Carenado sub forum. Personally I'd opt for the A2A 172 or even the A2A 182 (disclaimer: I have all of those aircraft). Cheers

I found an interesting issue when attempting to log into microsoft.com (via web browser) where I was unable to enter a password due to the cursor instantly tabbing out of the field automatically. I managed to trace the issue to Microsoft's web page code identifying my x-56 controllers as XBox controllers and running alternate XBox controller code. The issue was intermittent, only ever affected the microsoft.com login page and it didn't matter what web browser was being used. Sometimes it wouldn't occur for months, then I assume some MS code bro would make a change and mess things and later some other code bro would set it right and things would work again as they should. As a work around I found if I nudged the x-56 throttle forward just a little, the auto tabbing would stop and I could type again. Goes to show there can be many strange and unexpected issues affecting things. Cheers

Hi @shawnlund You can download the entire mod package and decide yourself what you want to use from it. Remember it's essentially @whamil77 's 6.1 release with fixes as I could do. If you're still interested please PM me your email address. Cheers

Both 4.5 & 5.3 have their pros and cons. A big pro for 4.5 (for myself at least) is that I can use TomatoShade and a custom cloud shader along with various custom programming I've written. Plus in 4.5 there tends to be few to no issues with effects and airport and scenery excludes. I have mostly Orbx scenery and airports, both of which do give issues in P3D v5 noting Orbx standalone airports are generally Ok in v5, infact Orbx Central will only display those they classify as compatible, however sometimes that compatibility makes for a worst product... e.g. Orbx 11S was made compatible for v5 and subsequently introduced many areas with overlapping scenery objects, I reported this to Orbx where they said "oh yeah, we'll look at that later in a service pack" and then never resolved the issue (luckily I had backups and was able to resolve the issue for 4.5 by rolling back selected files). Additionally, their supplementary airports included in regions were mostly not updated and leave a lot to be desired... and the same applies for many other developer releases. Mostly though you can fix these yourself if that's something you want to actually do. V5 does improve performance, especially in the area of background loading and decompressing of ground polys and scenery, although I never went to 5.4 due to the bugs that version contained that LM were never going to resolve (and never did). I've managed to customise some of the v5 shaders and truesky cloud configs, still it comes with built in effects issues (as effects need to be updated to the v5 format), has, imho, too high a level of base haze, truesky clouds are poor and are high GPU users. Of course if you're flying a base v5 sim with little in the way of third party products you might find it just fine. Most of the v5 issues stem from the fact MSFS2020 was released and a quantum shift to MSFS2020 occurred thus forcing developers to move to MSFS2020 if they wanted to stay viable, leaving P3D in the dirt and never allowing the third party's a ROI to update their products, plus LM themselves share a degree of responsibility for not having the foresight to see what was about to hit them. A similar thing is going on with MSFS2020 and MSFS2024. Cheers

Not sure about the process of "moving" a PMDG license, but for P3D itself there are a limited count of activations initially assigned to your purchase, hence the recommendation to deactivate and thus keep the count of activations in your favour. Once you exceed the activation count P3D will no longer activate and you'd need to email P3D licensing for a reset stating your reasons for a reset. Cheers