c912039

I run a few extra PCs to support P3D. I run NavDataPro and Navigraph charts, vPilot client and Aivlasoft EFB all on a Surface Pro, which I think lends itself perfectly to provide an easy convenient interface to utils that benefit from running on an independent screen/interface. I have other networked systems (4) running other tools which tend not to require user input once the flight is set up and underway.

Thanks for the info. To be honest, Im surprised if Im CPU limited - Im running a 8700K with HT on at 5.2GHz all cores with water cooling, and my temps are around 56 deg C under P3D load. Ive locked my frames at 24fps in P3D. My 1080Ti is also water cooled and also running around 50 deg C under heavy load. The strange thing is that the underlying tiles/textures can be seen, its just that these large white tiles keep flashing over the top, disappearing (showing the correct base tiles and then reappearing again. My main P3D window is displayed on my primary desktop screen, but its set to panel only, so essentially its all black. The outside view are a new window (no VC) and moved to the triple screens. The 2D instrument panel is another window on the primary desktop screen, sitting over the top of the blank/black main P3D window.

Can anyone suggest why, or where I need to investigate in P3D4.3, to work out why I cant use a 'Terrain: Level of Detail radius:' value greater than 'High' without having major scenery/tile issues when at altitude? When set to HIGH, scenery appears normal throughout the entire flight. But if I increase this to Ultra, or Max, I start to get large white/light blue tiles appearing/flickering when at altitude. At Ultra the tiles start to appear at mid distance and extend off into the distance and flicker on and off. At Max they appear directly ahead and off to the distance. Changing this value whilst in flight back down to high, removes the flickering large white/light blue tile issue. My setup is somewhat non-standard, but I am using a 1080Ti GPU, triple screens for outside view, plus a screen for 2D instrument panel. I have a 2nd graphics card for 2D instruments only. GPU monitor seems to show that I dont seem to be using more than about 1/2 available GPU Vmem, so Im baffled as to what might be causing/triggering this issue. Regards David

Hi, I have an ASUS Z370MB, 8700K CPU with an AIO water cooler. I have configured manual overclocking in the BIOS, and Ive been able to overclock to 5.1GHZ on all cores (setting each individually, and not synced), and under load my temps are 55 degs @ 1.37V. P3D would seem to benefit from as higher clock rate on core 0 as possible. As I currently have very stable temps at relatively low V with my current overclock, I was hoping that I might be able to bump up the clock rate on core 0 to something like 5.3GHz. I have set the clock rate on core 0 to 5.3 in the BIOS, with the remaining cores at 5.1, however I'm not sure that W10 is actually running with a higher freq core 0. I'm using HWInfo to check the individual core freqs when running P3D, and all cores are reporting back a max speed of 5.1, including core 0. What am I doing wrong?

One advantage with the way XP is installed, means I can delete and permanently banish it from my SSD in one quick command.

Hi, Yes you can. I run many add-ons remotely on networked PCs. I actually use 4 additional PCs (Viirtual PCs, as it happens) for this, but I could have used just 1 additional PC instead. I have set up: #1 - "PRE-FLIGHT PC" - used for flight planning, remote refueling/loading apps #2 - "WEATHER PC" - where is run WX apps, AS4/16,ASCA, SkyForce, FSGRW plus Envtex #3 - "ATC PC" - running ATC programs, and where I load SAPI voices #4 - "LIVE PC" - where I run apps that either monitor, or require pilot interaction, such as FSRealTime, vPilot Remote, EFB type apps, VA's ACARS, Traffic managers, multiuser apps such as FSCloud, JoinFS. Apps that can work remotely fall into 2 categories depending on what method they use to communicate to your HOST PC 1. FSUIPC via WideFS 2. SimCOnnect In general I set up each of my remote PCs to provide both SimConnect and FSUIPC/WideFS connectivity. An additional requirement may be that you need remote file access to Windows config files located on your HOST PC, as well as access to the directory where P3D is installed. If you do decide to utilize a networked setup I recommend the following plan. 1. Get basic TCP/IP connectivity working between the 2 PCs (use the command line PING util to confirm the 2 can talk to each other) 2. Get remote share mapping working so that the remote PC can mount and view your P3D files on your main PC 3. Purchase and install WideFS (part of FSUIPC) and confirm in P3D that it has acknowledged a remote WideFS client to connect 4. Configure SimConnect config files on the P3D HOST and remote PC 5. Now start to install your apps on the remote PC If you dont get the fundamentals right and follow these prep steps in order, it can lead to great frustration when your remote apps dont work. Regards David

I am also after a tiller I've come across this page, which looks like its available, although the English version of the website doesn't have a translated page https://primecockpits.com/produto/steering-airbus/ Ive got a large number of GoFlight modules and 3 GoFlight DIO boards, and a Leo Bodnar card all interfaced through GIT. From what I can work out on that page is that their tiller will need to be connected to something like the Leo Bodnar card to get it working. Regards David

I am using GIT with SECM (and almost all the other GF panels) very successfully with both default and non-default aircraft. I thoroughly recommend it (and I have no relationship with the product or the company behind GIT, other than to be a very satisfied customer). I'd be happy to help you with any config or bespoke configurations for your aircraft in P3D using GIT.

Hi, Would it be possible to add support for this 2 letter Airline code please: FD (Royal Flying Doctor Service) Many thanks

Hi, Ive got quite a lot of GF modules. I had some issues in the past, and found the following: 1. Ensure your USB chipset driver is up to date 2. try to use native USB2 ports instead of USB3 ports 3. Always use a powered hub to connect multiple GF devices. Allow 500mA power per module, and ensure the power rating on the PSU for each hub can easily match that requirement. 4. Limit the number of GF modules per hub - I connect only 4 or 5 per hub, based on te particular brand of hub I use 5. Ensure you turn off power save mode for each port and hub in your OS Windows 7 & Windows 10 have different methods to set this 6. Anytime you plug in a new hub, module or switch USB port, recheck the USB power save setting. 7. Use the latest GoFlight driver I can highly recommend using GIT from Pollypot Software to program your GF modules (works with FSX/P3D/XPlane) http://www.pollypotsoftware.org.uk/ Regards David

Try this one: http://www.bradleymarsh.com.au/homepage/A320Info/Geezer%20Guide%20-%20Jetstar%20101202.pdf Its written from the CoPilot perspective, but you can probably adapt it for Captain as well.