January 29, 201610 yr Hi, I have the problem that the NGX is not being recognized correctly in OC (see screenshot). Since this system has no FSX installed (and never had), I guess it's some registry entry / directory that makes OC think that there is another version. The plane itself is working perfectly fine, I'd just like to be able to install liveries and possible updates via OC, which is not possible right now. Any ideas? EDIT: Forgot to mention: Win 10 x64, Prepar3D v3.1 It was working a few days ago, so it must be something added by some recently installed stuff. Oliver Grützmann
January 30, 201610 yr Oliver, you are right in suspecting something corrupted the registry entry... submit a trouble ticket at PMDG Product Support and maybe they can help you with some tools they have available. Hopefully, you are NOT using any kind of migration tool. Dan Downs KCRP
January 30, 201610 yr Author Oliver, you are right in suspecting something corrupted the registry entry... submit a trouble ticket at PMDG Product Support and maybe they can help you with some tools they have available. Hopefully, you are NOT using any kind of migration tool. Thanks for the advice, Dan. Will do so. No, I don't use any migration tool. I'm using some older sceneries (FSX, P3D v2 etc.), but I only used native v3 installers. Anything else I install to completely different directories, or, if possible, completely manually. Can't even tell when exactly this happened. I don't use OC too often. Oliver. Oliver Grützmann
January 31, 201610 yr Author Just to get back here, problem is solved. it was indeed a registry issue, some addon changed the SetupPath of Prepar3D. I got there since the support suggestions didn't help, so I tried to uninstall and reinstall the NGX. The NGX installer was not able to locate the P3D executable, which made it quite obvious. Not sure why any installer would mess around there, but it happened. After setting the correct path, it's works again. And btw, great support, sending an answer on sunday Oliver. Oliver Grützmann
January 31, 201610 yr Not sure why any installer would mess around there, but it happened.After setting the correct path, it's works again. It's a shame not all developers are careful with our stuff..., hate it when strangers mess with my stuff. Thanks for sharing the fix, it will certainly help others. Dan Downs KCRP
Create an account or sign in to comment