General Category > General Discussion

Dino's T-45C Goshawk version 1.85 & Javier Fernandez's Nimitz carrier released

(1/3) > >>

JamesChams:
For all you FSX Naval Aviator enthusiasts,

Just released FREEWARE: Dino's T-45C Goshawk version 1.85 & Javier Fernandez's Nimitz and Eisenhower nuclear carriers.  Click Here for UPDATE: AI & USS Carrier Missing Sounds Fix.



Enjoy!  :D

FalconAF:
OK, got a question about this.  I downloaded the above 2 items, and the carrier package said it recommended the use of AICarriers2.  So I downloaded that also.  It required the Jave app JRE, so I installed the latest version of that also.  Order of install I did was:

1. JRE
2. AICarriers2
3. Nimitz carrier download

I never got to installing the T-45 because when I started FSX, I kept getting an error message saying that the Virtuali bglmanx was hosed now.  It gave me the option to run it or not, so I tried it both ways.  Either way, I now have no building at any of my FSDT airports...just the jetways like if I had used a demo and the time ran out.  In my root FSX folder, I have the following 4 "bglmanx" files:

bglmanx.dll
bglmanx.dat
bglmanx_fsdt.dat
bglmanx_aerosoft.dat

ALL of the above files now have "Date Modified" dates of 4/18/2009 5:40 AM.  That's when I did the installs of the above 3 items.  I uninstalled all 3 items above and still get the error when starting FSX.  File names and Date Modified are still the same also.

Any ideas what the heck happened and how to fix it? 

JamesChams:
The BGLMANX.dll issue is NOT related to these packages.  It is a know issue with installs of FSDT sceneries.  Virtuali has indicate (in several posts) how to resolve this.

HERE is one solution: http://www.fsdreamteam.com/forum/index.php?topic=804.msg5829#msg5829

virtuali:
Please, let me know if I understood correctly: your bglmanx worked fine, but as soon as you installed the above packages, you started to get the error ?

If yes, it's probably the usual FSX error, that FSX gets confused when a new module is trusted, and creates issue to other installed modules that always ran before. In this case, the module you trusted was probably AICarriers.

The solution is always the same:

- Try to install any of our products again, or the stand-alone Addon Manager. This will get you the current version of our files, just to be sure.

- When FSX says the module might not work, ignore it and allow the module to run. Don't worry if it crashes FSX, just try it again.

- If it doesn't run on the 2nd try, reboot Windows and repeat the procedure

virtuali:

--- Quote from: JamesChams on June 19, 2009, 02:10:37 am ---The BGLMANX.dll issue is NOT related to these packages.  It is a know issue with installs of FSDT sceneries.  Virtuali has indicate (in several posts) how to resolve this.
--- End quote ---

It's not an issue of FSDT sceneries. It's a KNOWN FSX bug that AFFECTS our sceneries, but just because we use a module to run them. It affects any other module or gauges: I get it randomly (meaning, it doesn't happen very often, but it DOES happen) on pmdgoptions.dll, wilcopub.dll, leveld.dll, etc.

It always happens when a newly installed module has just been trusted: something in the Windows trusting system goes bad, and random modules fails when run the first time a module is trusted. I think it's probably a Windows issue because, usually, a Windows reboot fixes the problem.

Navigation

[0] Message Index

[#] Next page