ARRRGGHHHHHHHH! So...... 2 hours later, a full uninstall of FSX using PMDG's knowledge base article, and full re-install of totally fresh FSX + Acceleration, using PMDG's knowledgebase article, and with no other addons. Installed NGX, and loaded the 737, ............no activation process.......... ...........no initiation, no gauges, no hope left. Gutted. I really can't believe this is happening with a PMDG product. Since raising the ticket with PMDG yesterday, all I've had is 1 reply from Ryan requesting whether I have stopped any Windows services from running, and to confirm my Windows is set up on US-English. I've sent 3 further responses, information, and a copy of my DLL.XML but this mustn't be a high priority matter for PMDG support. I guess this is a case on software security / piracy prevention causing a loyal, paying, supporting customer not to be able to use the product they've bought. 3 days into attempting to activate the NGX is looks like I still won't be flying it today....... David.

Hi I did experience a similar problem. Mine was solved when reinstalling FSX and NGX on an other location then previous. Maybe that helps you as well. If that's the case i think something is messed up in the registry after reinstalling fsx and NGX. Good luck,Jeffrey

While I wait for PMDG to reply to the support ticket, would anyone be so kind as to post a copy of the DLL.XML entries relating to their NGX, so I can compare them with mine and adjust if necessary. After (now 30+) attempted installations / activations of the NGX, the only entries that show in my DLL.XML for the NGX, appear to be for the HUD ......so maybe that is the problem. The PMDG knowledgebase contains some info about this, but it does not contain specific details of what entries should appear in the DLL.XML, or the NGX. Thanks in advance if anyone can help. David.

While I wait for PMDG to reply to the support ticket, would anyone be so kind as to post a copy of the DLL.XML entries relating to their NGX, so I can compare them with mine and adjust if necessary. After (now 30+) attempted installations / activations of the NGX, the only entries that show in my DLL.XML for the NGX appear to be for te HUD ......so maybe that is the problem. The PMDG knowledgebase contains some info about this, but it does not contain specific details of what entries should appear in the DLL.XML, or the NGX. Thanks in advance if anyobe can help. David.

Hi Stick, Try the following procedure:Insttal this software:http://www.iobit.com...temcareper.html After that perform a full unisttal of your PMDG NGX again and reboot your PC! After rebboted, performe a registry clean with the System care! After cleaned, install again your NGX and let us know if thsi procedure worked for you.

@ SSSILVABR Thank you sir, I will try that now. Regards,David

Thanks for trying to help Silvio, but after trying it, the problem still remains. I am starting to think that only PMDG can solve this one by looking deeply at how their activation software is working (or not it seems), in scenarios where the NGX was installed previously (ie..reinstallation scenarios). Either that or the DLL.XML is wrong in my case ....... still waiting for a response on the ticket for that. Cheers.David

I would ask again whether anyone could copy the text (relating to the NGX only), from their DLL.XML file (which lives in the FSX folder that also contains the fsx.cfg file), so I can see how the DLL entries for the NGX look. I can then compare them to mine. PS..... Pretty disappointed with the total lack of response on my support ticket from PMDG. I have sent info, descriptions, a copy of my dll.xml file, but still not even an acknowledgement to reassure that this is being looked at ..............

I do not see a ticket from you anywhere in the system right now. Is Stick your real name? If not, I suggest you start following the forum rules and using your real one.Did you miss the part where it says to expect 24-48 hours for a ticket response too? You're posting messages just a few hours apart on how disappointed you are with our response time when I've cleared out every single ticket well within that timeframe. My *average* response time including all the craziness in the days just after release is under 6 hours.

Hi Stick, In PMDG site support you can see how to fix the dllXml. See the link: http://support.precisionmanuals.com/KB/a92/dllxml-information-and-troubleshooting.aspx

The NGX uses the dll.xml for one thing - the HGS, that's it. There are no dll.xml entries for other gauges the way there were with the MD-11 and 744. The only problem a corrupt dll.xml causes for the NGX is a blank HGS display.

The NGX uses the dll.xml for one thing - the HGS, that's it. There are no dll.xml entries for other gauges the way there were with the MD-11 and 744. The only problem a corrupt dll.xml causes for the NGX is a blank HGS display.

Ryan, I already sugest to open a forum only for customers registered so I believe that the time spent with fixes will be only for original products. I can not understand a lot of problems to still be solved after thousands hours from beta tester and years of development.

Silvio, The fact of the matter is that we don't see these issues ourselves. We can't fix what we can't reproduce on our debug systems. There's literally millions of possible combinations of hardware, Windows versions and configurations etc. It's impossible to account for every single condition.

Ok Ryan, I understand and agree with you. For the next produt consider increase the number of possibilities in Beta tester team. Thanks

I just want this known for anyone who thinks we're doing a bad job at support due to this Stick's comments in this thread - I just located his tickets sitting in a part of the queue they shouldn't have been in... (which explains why I didn't see them so far today) HOWEVER:His first ticket came in at 6:26PM my time last night. I responded to him SIX MINUTES later at 6:32PM asking for more info. He replied at 1:53AM after I'd gone to sleep and followed with two more tickets asking why he hadn't been attended to yet at 5:45AM and 5:51AM. I woke up around 9:30AM this morning and started working support around 10AM. Seriously? Not replying in the middle of the night while I'm asleep is poor support? Even if I hadn't responded to his original ticket yet at this very moment, that still hasn't been even 24 hours since he submitted. We state 24-48 hours for responses even though we're typically far below this as evidenced by the six minute response time to the original ticket. Quite frankly this is ridiculous and I am absolutely sick and tired of these unreasonable demands being put on us. We are real people David, we need sleep just like you do - expecting me to be on call to reply to you at all hours of the night and then coming here to complain about our terrible support when we don't is positively insane.