Dave CBFS

They're on .ORG these days, not .COM

Probably need more time to get all the bugs in.

Make sure you're in the interior view of your aircraft when you first open the Airshow Assistant UI, otherwise it doesn't always initialise properly. Then you can switch to exterior view if you like. All you need to do is click the "cover me" button and one wingman should appear. You can then add up to 4 with the slider.

Useful tool @MammyJammy, however it seems to miss some textures, leaving them at 4096. For example, "FSLTL_A20N_ANA\TEXTURE.ANA\FAIB_A320_PW_T.png.dds" does not convert, but "FSLTL_A20N_AMU\texture.AMU\FAIB_A320_PW_T.png.dds" does.

You can turn it off anyway.

Look here: http://forum.simflight.com/topic/80239-p3d-version-3-fsuipc-menu-entry-not-appearing/

Have a look here:http://forum.simflight.com/topic/80239-p3d-version-3-fsuipc-menu-entry-not-appearing/

If you position your mouse at the bottom of the menu window you should be able to drag it down and enlarge the window.

Looks like your FSX hasn't been updated to SP2 or Acceleration.

I had this also. The texture files were in a separate texture folder referenced in the texture.cfg, but for some reason weren't loading. Putting them in the main P3d texture folder worked though.

Mine's worked since day 1 with P3dv2 & 3 on Win7 and now Win10. I don't use Target. Everything is assigned and calibrated via FSUIPC and / or LINDA.

I purchased a license a couple of days ago & it didn't cost anywhere near $100! 5 Euros, £3.50 which about $5.30 in fact. Works really well, using an old Android tablet. Thanks Mark for a simple, low cost solution. :smile:

On the display settings page, there is a check box marked "black out desktop" (or similar wording - not at PC at the moment). Make sure that's not ticked.

Yep, just tried it here & got the same message. Running the latest version (1.10.6461) of the NGX in P3d.

In case you didn't know Rob, there is a demo version if you want to try it out first. It works fine with the NGX in P3d.

They'll be listed under Boeing, not PMDG.

No idea if they're needed, just pointing out that there are files in one patch that aren't in the second.

Hotfix 12943 contained Particle.fxh & ParticleCS.fx in the ShadersHLSL folder, but HF 12944 does not.

Tried this yesterday. I found it does work but I need to have the "blackout desktop" checkbox ticked (I run 2 monitors, but the second is used for extra programs rather than P3d itself). The display did look better, but suffered from stutters, although the frame rate was fine. Maybe my 760 wasn't quite up to the task. When the correcct desktop drivers are released, I'll give it another go, but for now I'm back on 344.11.

I wonder if this is the same issue I noticed with some afterburner effects that were rendered at approx half size? P3d V2.3: P3d V2.4: I copied over the "ParticeDraw.fx" file in the ShadersHLSL folder from my 2.3 backup and the fx went back to the correct size.

Thanks for the info Rob. BTW, Pete Dowson is away again at the moment, so FSUIPC won't get updated until sometime after his return on the 7th October.

Can't see anything wrong in the picture you've linked to, apart from general anti-aliasing. Looks exactly like it does in Google Earth.

It appears LM have made some changes to the XML parser which has made it more strict on the syntax. If you add the line: GaugeDevDebug=1 to the [panels] section in the Prepar3D.cfg it will throw up an alert if it finds a gauge or embedded XML that has incorrect syntax. Try that and load up the 146 & it spits out error after error!

The wheels being embedded in the ground is because the gear suspension isn't working properly (or at all!), not due to the contact points. If you load up the 146 in P3dV2.1 and then FSX and compare the relative positions of the wheels to the gear doors you can see this.

I tried enabling VC shadows for the NGX but it didn't didn't work properly. The shadows only showed up on some parts of the side consoles. Maybe the way PMDG has set up their materials?