bcrawley57

I have the latest Aviaserver and the CDU is working perfectly on my Ipad. However I cannot get the web address for the overhead on my second PC. It worked previously on 2020 777. This is the web address I am using. 192.168.0.136/ovhd/777/777/_pax.html. UPDATE: Sorted I added the number taken from the QR code and it works now.

Please let us know if you find a way. I really miss this sin 2024.

I wish I knew what you meant by the viewpoint problem. :o

Hi Byork, Are you referring to a client only uninstall and install?

Definately, it would be interesting to see how different it is and what new technologies may have been introduced.

Thank you for your reply. Yes I did install version 1.9 with vehicles, a fresh down load. The problem is the same as the forum link you kindly inserted. I am mid flight at the moment, so I will check out any recommendations in that other post. It has only started since the 1D update of PMDG so may be an issue with that update. Kind regards,

Problem still persists after reinstall of GSX, I guess I just have to live with it.

Did a reinstall of GSX after an uninstall and problem persists.

I know this will probably sound bad, but where do I do that from? Kind regards,

Colleagues, Since the last update, I have noticed with GSX Ground crew that it does not recognise that the front passenger door is open. To start loading passengers, I have to close the door, to then open it again. I always start from cold and dark, has anyone else experienced this issue?

Byork, Thank you for responding, actually I think the problem is more likely to be with GSX as it is it's failure to recognise the door is already open. I have to close it, only to open it again before they will load the passengers. I have so many add ons I get confused, it is not FS2 Crew that is at fault I think unless you can think of anything that FS2 Crew is doing when the door is first opened. I will have a look on their forums. Apologies for the mix up.

Although this is extremely minor, since the latest NGX update, when I am starting from cold and dark, FS2 Crew fails to recognise that the door is already open when loading passengers. I have to close it and then open it again. Is that a bug or am I doing something wrong?

I had a similar issue all of a sudden on mine before Christmas, although it happened at between 1hr 35 and 1hr 50 into flight. Like you I tried everything, raised tickets with PMDG and had some online experts look at it. Same symptom in just decided to veer of course and nothing would let me bring it back on course. I never got to the bottom of it, I sent Tech support the saved flights and nothing. In the end I tried install and uninstall of NGX, exactly the same happened again. In the end I totally reinstalled FSX (drastic I know). That solved it. Although I never worked out or even found out what caused it, it happened after an install of Pro ATC, which gives some Co Pilot functionality, not to say thats what caused it, but like you with it being my main jet, I am afraid to try Pro Atc with it incase it was responsible. Let us know if you find an easier solution than me and good luck with it, I know how you feel. :(

Thank you, I will try and research if my motherboard will support it. It is currently a stock HP envy device, so I am not too hopeful. Would overlocking be done in the BIOS or by other means. I imagine I would have to improve cooling too, although I have already beefed my Power supply to 650watts, they never come strong enough.

I am toying with replacing my processor from an i7 4770 to an i7 4790K as,ming my motherboard support that would I see an improvement in performance?

The Saitek drivers on their web site. It comes under the Madcatz section I think. http://www.saitek.com/uk/down/drivers.php You just need them for the panels that are not supported by P3D and FSX directly.

The disconnect issue is normally found with Windows 8 and although irritating, it can be fixed. With the 777 I have always used the Saitek Proflight yoke as well as many other Saitek products and they all work really well. As with the previous person, I have disabled all FSX controls and have all the mechanical products working through FSUIPC. The other panels and instruments, I use the latest Saitek drivers for and they all work well. I did have an issue getting the panels to work on P3D, but I have simply copied the Exe.dll file from FSX to P3D and they all work again. Although the yoke and rudder pedals/throttles work straight away with P3D, I have again disabled them in favour of FSUIPC.

Well, I am just happy that on this chilly Sunday morning I can finally get at least the 777 on to the P3D platform. Given the amount of flying I do, nearly 300 hrs in the NGX that works out at quite a small amount of money per flight for a few hours entertainment. We are also supported by the excellent after sales support and upgrades that PMDG offers. Thank you PMDG for completing my weekend. Just give me a few weeks to save for the NGX on P3D please

That explains my issues too, so this still occurs even with failures disabled?

You can also use buttons for reverse thrust. I have programmed the spoilers in a similar way on my Saitek throttles. There is a button behind each detent on the quadrants and I have programmed them using FSUIPC. The throttle reverse are programmed for each engine using the commands throttle 1 decrease and select repeat when pressed, you select the command throttle 1 cut when released. You have to have programmed multiple throttles as opposed to the single linked throttle for the two engines. For me that gives a realistic experience. The spoiler armed is a similar button and is programmed through FSUIPC on this occasion I select Spoiler Arm Toggle when the button is pressed. No repeat or release actions need to be programmed.

Agreed, I just want the product and the price, they make flight simming worthwhile in my eyes. Well done PMDG

Where is the cameras.cfg please? Brian Crawley

Looking forward to this release. Hopefully Virtual Avionics will be producing an add on so we can have the FMC externally? Happy New Year to the brilliant PMDG team. Heres to a successful 2015 and beyond for you.

I have raised a ticket, not heard back. However further research, I understand that occasionally there can be port conflicts, a fellow VA pilot changed his port settings from 9000 to 8800 on both the programme and the app on the iPad. This worked for him.nnThe port setting can be changed in the VA Interface ini file within the installation folder. Personally I have since totally uninstalled any reference to VA interface and completed a fresh re-install. It is working now on the default port 9000. I hope your problems are resolved too, I know how much it hurts when this app stops working. (Apologies for omitting the full name) Merry Christmas to all too

I have had problems getting it to rum. It appears the Windows Essentials and Windows Firewall is blocking it. Even though I have added it to both the Firewall allowed list and Essentials excluded list. Anyone got any other suggestions, or know of protection that will allow it to work? Kind regards,