Rogen

Just an addendum on this. While flying around Rio I noticed a block of highrise buildings in the water just off the beach. Turns out it the buildings were default objects that end up in the water after Orbx Vector corrects the coast line. And there is a simple fix available over at Orbx, see the below thread. https://orbxsystems.com/forum/topic/197440-odd-floating-high-rise-buildings/ Before Fix: After Fix:

Let's see now... Yes there are all the Orbx products you've listed. Plus there's AI Shipping, TerraFlora v2, Rex Texture Direct, Drzewiecki Design HDGrass, Terra Emergence Project v1.6, TomatoShade, ReShade, car/truck ground speed is custom, custom night sky and stars (I know not visible here but at night it's great!), custom water, FreeMesh and probably a few more, I think I should get a spreadsheet together just in case I have to rebuild from scratch. Yes the autogen sliders are maxed, but there is more, the "spice" of being able to control via the prepar3d.cfg with settings such as the below. People say things like you shouldn't need to tweek a sim config, but I say hey! that's where the power of control is available and I prefer to use the power LM have provided. Cheers

Maxing out the autogen while touring around Rio De Janeiro in the Avro 621, scenery is Orbx with a few addional spices. Cheers Al Shipping, an amazing piece of freeware no one should be without, brings the water to life, the efforts of those who contributed make the package what it is. And finished for the day's flying.

You can add additional auto discovery paths, I don't actually use the one in the Documents folder. For example I have the following where I just drop in the containing folder with its add-on.xml under it. Then sim starts sees the new addon and away we go. I also use the Lorby tool to manage.

Hi Folks, Going through my aircraft archive and came across the illustrious MilViz P-38 Red Bull freebee. I'd downloaded it some time in the past when i was running P3D v3 but never got around to installing it before moving on to P3D v4. Of course the aircraft is not officially for P3D v4 but I thought I would give it a go given there is already a Milviz P-38 included in P3D. First hurdle was the installer doesn't give an option to select a path, just radio buttons to select the sim (FSX/FSX-SE and P3Dv2/3), this was overcome by setting a dummy P3D registry key. e.g. [HKEY_CURRENT_USER\Software\Lockheed Martin\Prepar3D v3] "AppPath"="E:\Lockheed Martin\Prepar3D v3\" The installer then unpacked everthing into the path giving me the folders of. Effects fonts Gauges SimObjects This I placed into my add-ons Milviz auto discovery path under the title of H:\Addons_P3D\01.Aircraft\Milviz\Milviz_P-38_RedBull along with a custom add-on.xml So far so good, Sim was fired up, the P38 was discovered and gave it a flight test. And the usual "no cockpit sounds" was the first issue, plus the landing light was a tiny little light without any throw. To fix the sounds required 3 changes: Rename the Milviz_sounds folder in \MilViz P38 Lightning\panel.Restored\ to MVSounds. Copy the MV3DSound.dll from the LM Milviz P38 into \MilViz P38 Lightning\panel.Restored\ Comment out the original sound gauge in the panel.cfg and add the following. gauge00=MV3DSound!MV3DS, 0,0,1,1,SimObjects\\Airplanes\\MilViz P38 Lightning\\panel.Restored\\Milviz_Sounds#19 There are two places to add the above, [Vcockpit01] and [Vcockpit05] At the same time I took the opportunity to add a shockwave light as a landing light plus make a few titling changes in the aircraft.cfg file and add precipitFX effects. light.12= 5, 0.85, -20.45, 0.95, fx_shockwave_landing_light_narrow // Shockwave light Results: Not too shabby, it's a bit finicky on the start animations but follow the instruction in the quick start manual and it starts fine. Be nice if Milviz could revisit the aircraft and make it fully compatable given LM's inclusion of another Milviz P-38 on P3D x64, doesn't seem that it would need much. Is it perfect? nope, what it is though is pretty fun to fly and sure is *shiny*. Cheers

A next gen GFX card probably, I know I cannot max AA out on mine (GTX 1070Ti) but perhaps these threads will help. One thing to note when using Sparse Grid AA is that a matched MSAA value needs to be set in the app. For example if using 4 x SGSSAA within NVidia Inspector, then P3D should be set to 4 x MSAA, this is because SGSSAA needs the matched MSAA values to optomise the SGSSAA output, you can vary though as shown in the threads. DSR is also pretty good to use as it will resize/resample and result in a smoother less jaggy display, the smoothness of which can be controlled via the Nvidia Control Panel, the extra screen size though makes it even harder on the GPU for AA. You'll need to monitor the GPU use and tune values so as to not max out and subesquently kill the frame rates. Cheers

Well, I don't have VR nor P3D v5 as yet, that said it does work on P3D 4.5 (my current). When running unlimited in P3D the FFTF value is hardcoded to a low value, something like 0.01 and any value set in the prepar3d.cfg is ignored. With such a low FFTF value frame rates tend to be at their max (unlimited) because the engine is spending hardly any time rendering scenery. A side effect is "the bluries" and/or a lack of scenery precisely because hardly any time is being spent rendering scenery. I therefore use it to prevent "the bluries" and allocate more time to scenery rendering when running unlimited in P3D, and it does certainly work in my testing with it off/on. Essentually it gives control over the FFTF value where previously there was none. Worth it imho. Cheers

Yes ShaderHLSL should be located in the root of the P3D install directory. The are the source shader files the sim compiles for shader cache use. Normally such folders are not removed (although hasn't a few Windows bugs resulted in folder/files being removed?) I've seen a lot of so called missing folders accidently dragged into other folders nearby, hence missing but can be found with a search. The recycle bin is another first point of call. Could also be something really weird like it has become a hidden folder, or lost ACL permissions, or a disk corruption issue is developing, or AV has picked it up and deleted/quarrentined, or some unknown bug in an update has taken a fancy to the folder and its tasty files inside and swallowed the lot 🙂 Otherwise a repair of the P3D client should bring them back. Would be interesting to hear the outcome. Cheers

You'll find the prepar3d.cfg used for the flight in the thread (in a spoiler), it does have selected comments within and there is further config discussion in the thread itself. The shaders customisation consist of hand edit to PrecipParticle.fx for rain and snow. //Control how long streaks face and how big they are. float height = cb_fQuadSize * cb_fQuadSizeHeightScale / (2.4 - (cb_uPrecipType * 1.65)); float width = cb_fQuadSize * cb_fQuadSizeWidthScale / (1.0 - (cb_uPrecipType * 0.25)); Active Sky Next changes are just running through the config options and setting to what I liked the look of, i.e. try and max it out then back off till performance is the desired. Rex Direct Texures changes are using lower resolutions for clouds (2048 and 1024) and DXT5 textures for same (Plus a whole lot of theme building based on what I liked). And the NVidia inspector config export can be also found in the thread, you'll need to log into Orbx for that though. The goal was to configure for max settings while still remaining in VSync on a GPU challanging flight, be that just around 11S... Lots of trialling given @ 30 Hz a 10% increase or loss is just 3 FPS. I note in the latest driver from NVidia (I'm running 446.14 atm) the Silk Smoothness option has been removed and it's noticable for myself at least. I might end up rolling back to earlier version driver given I'll be sticking with P3D v4.5 till at least the beginning of next year and apart from loosing the Slik Smoothness option I've not seen any real difference in performances with driver changes of late. Cheers

Cheers

Hmmmm, looking at that vid again I think I did :-) Again it's having the right hardware and the right tune. Of course LM could certainly do a little better at their end. But hey, more competition usually gives a kick up the A. Cheers

Your missing the point... The main trick is to be able to maintain enough FPS to enable a Vsync. That little run around 11S was consuming vast amounts of GPU - into the high 90% and was also a very high load on the CPU, all locked at a 30 Hz Vsync. Anytime a GPU is maxed out 100% the framerates plummet and introduce a stutterfest, that's just the nature of what happens when the hardware is overloaded. The vid is about tuning to achive max performance and looks for a smooth Vsync. Cheers

Hmmm, I beg to differ in that regard. With the right equipment and P3D tuning a very smooth experience can be had. Take the example vid in the link below (and it's not even v5). https://orbxsystems.com/forum/topic/188575-p3d-v45-maximum-detail-and-performance-tuning-test/ The thread also has info hardware/software and how the result was achieved. Cheers

Hey folks, Came across Gibson Enroute Sceneries while exploring the web for flight sim related stuff. https://www.gibsonsceneries.com/ Interesting is that his Northern Territory scenery feature 2 x options. 1), where it is all the enrounte photo scenery 2), where the scenery features an area around the plane showing underlaying scenery e.g. Orbx with the enroute photo scenery for all further. A composite type of scenery if you like. There is a demo it you'd like to trial it out, an approx 900 x 450 KM area of the lower Northern Territory area which encompases Alice Springs and Uluru (Ayers Rock). This pic is of the full enroute photo scenery (even though it is enroute scenery it's pretty good, better than Megascenery in places as Mega Scenery is pretty highly compressed) This is same pic with the composite scenery where the Orbx layer (Australia v2) shows through in the area around the plane. Here's a few more of the area in my fav planes for the month the PC-9/A and the Flight Replica Super Cub. Cheers

This link help? https://devblogs.microsoft.com/directx/demystifying-full-screen-optimizations/ Cheers