General Category > General Discussion
Addon Manager **SOLVED**
ingoke:
Hi, it´s me again.
I calmed down a bit and did some more reading in this forum. For some reason I decided to de-, then to reinstall PHNL and guess what!? Everything is fine. I really don´t have a clue what went wrong during the first installation process.....
Flightsimming is more about computers and software than virtual flying. I spend about just as much time keeping the sim running as it should as I do in the air. :o
Hope you don´t hate me for turning nuts.
Ingo
virtuali:
--- Quote from: ingoke on January 22, 2010, 08:31:40 pm ---This evening I installed PHNL which lead to double entries in the FSX.cfg. I deleted the double entries (coutl.exe and bglmanx) in the trusted section and ran the stand alone addon manager installation again. Now none of your sceneries show up.
--- End quote ---
Double entries in the Trusted section is NOT an error. It simply means that a new version of that module has been trusted so, FSX will not repeat the trusting question again for that specific version. But, as I've said, the fact you have several entries for the same module, it's not a problem, at all.
The suggestion of removing the entries is not because just having entries (single or double, it doesn't matter), it a problem. It's because the FSX trust system cleary has issues because, the SAME module that the 1st time is trusted is wrongly labeled as problematic, it always run, either by launching FSX again, or by rebooting Windows. Removing all the entries, it's just a way to force FSX to redo the trusting question, nothing more.
--- Quote ---Explanations like some other programm has corrupted this and that file really don´t help, because no other scenery is that "vulnerable" or easy to mess up.
--- End quote ---
Explanation are correct. And no other scenery is "vulnerable", because doesn't use a dll module which, as been explained many times, does too much for the scenery and it wouldn't work without. But, it's absolutely not true that no modules are so "vulnerable", because if you simply look at other support forums, you'll see that everyone else that depends on .dll modules has similar issues, trusting issue, antivirus issues, etc.
This is the only major gripe we have on FSX: the requirement for all modules to be trusted, which is obviously bugged, and the dependency from the XML files to load modules. FS9 DOES NOT have all these issues, because modules don't need Trusting, and everything that is placed under the MODULES folder will just be loaded automatically.
--- Quote ---What can I do next without having to reinstall everything (something I really don´t have the time for)?
--- End quote ---
The first and easiest solution, is always this:
- Uninstall PHNL. Reply YES to the question "Do you want to remove the Addon Manager?" and replying YES to the question "Do you want to remove the Couatl engine?"
- Reinstall PHNL. If you see the Trusting message, trust all modules.
- If you see the "3rd party module" error message, keep ignoring it and ALLOW the module to run. Do this a couple of times. If it doesn't go away, reboot Windows and try again. It WILL go away.
Kevin:
I did a reformat just 2 months ago with the same exact settings. So yes your answer will be there's no fix, it's fscopilot BUT, why would this problem happen right now. None of my settings are any different on my computer. Have all the same sceneries and version of fscopilot. I just wanted to say I have never had any sort of issues with your sceneries. The fscopilot version has not changed in a very long time. FSDT sceneries do....that's why my conclusion would obviously be your sceneries.
KB
virtuali:
--- Quote from: kbpilot5 on January 23, 2010, 03:13:32 am ---The fscopilot version has not changed in a very long time. FSDT sceneries do...
--- End quote ---
The only thing that changed recently, it's the installer doesn't put our module before FS Copilot, as it used to do, in order not having blocked by it. This because we now use the standard MS XML parser to add section, which it's easier and more reliable, with strangely formatted XML files, but there's no way to exchange the order using that method.
That's why I've immediately said to try exchanging the loading order. However, if this doesn't change anything, I really have no clue. However, the undeniable fact is, as proven from the old post from 2007 on the Cloud9 forum, that FS Copilot was known to have issues with our module since 3 years already.
It shouldn't be strange that it doesn't work now: it should be strange that it did before. BTW, the FS9 version (which, as I've said, it's *exactly* the same .DLL that works in FSX as well), constantly crash on exit on my system, even if the FS9 WORKS with the FS9 version of our Addon Manager.
--- Quote ---.that's why my conclusion would obviously be your sceneries.
--- End quote ---
No so fast. There are other things that keep changing, and it's the various Windows updates, which over time changes a lot of system .DLL so, it's surely possible that, one of these updates has made the problem (that always existed) between FS Copilot and our own module, to reappear.
Kevin:
I think you need to consider a solution because your answer to everyone that uses fscopilot and purchases your scenery can not be install squawkbox. Addon Manager is ridiculous and has always been a pain.
KB
Navigation
[0] Message Index
[#] Next page
[*] Previous page
Go to full version