Dave CBFS
Members
-
Joined
-
Last visited
-
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.
-
Dave CBFS replied to marcom's topic in Aviasoft Remote CDU for Phone / Tablet Official Support ForumI 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.
