Military AI Works

Thanks for your prompt reply, I have not meddled with any aspects of the download content....would'nt know
where to begin, guess I'll just have stick with the orginal converted FS9 Hawk programme, all be it. not as beautiful
texurally as the new update, at least it rids FSX of the dreaded runtime error issue.

Kind Regards
Mike

OK so if I understand what you are saying you haven't altered the cfg in anyway.

So has anybody else had the runtime errors with these Hawks, and what effects do they use?

Over 1,500 downloads of the Hornet/Hawk packs, so far one other FSX user has reported a similar issue (with the Hornet). If this is a visualfx.dll crash then an incompatible fx_dummy.fx file could be the culprit. This file is a stock classic FSX effect, the same version is used in P3D, I have FSX-SE and it is not present there. To verify this is simple: Find that file in your FSX Effects folder and block it out by changing the name to fx_dummy.fx.BAK.

Henk.

I am not aware of the fx_dummy.fx file what does it do/contain and do you have any idea why it might affect a small number of people but not the majority?

Steve, for the Hawk/Hornets I added fx_dummy.fx as a dummy nav (type 3) light to the [lights] section to enforce the beacon/strobe lights (type 1 / 2). I do not want true nav type lights in AI because they come on before engine start and stay on for up to 15 minutes after shutdown. But, it seems the sim requires at least 1 nav type light entry in the [lights] section to enable the use of beacon/strobe type lights. This has been the case since FS9 and is still valid in P3Dv4.
After the Hawks/Hornets conversions I did not use fx_dummy anymore, the beacon/strobe fx are added as recognition light (type 7).

The classic FSX/P3D stock fx_dummy.fx should do nothing. My guess is that somehow the 2 users who seem to have visualfx.dll crashes (which is yet to be confirmed) have a different version of fx_dummy.fx, maybe from some add-on.

Another reason to suspect fx_dummy.fx is that the other effects used for the FSX install of the Hawks/Hornets are standard FS9 MAIW effects like fx_f16_navgrem.fx.

Henk.

Henk, as I am very familiar with the workings of effects in AI would you mind sending me the fx_dummy.fx and I can see if it is AI proof.
If it isn't it is easy enough to fix.

I seem to keep getting this error message when I have the T1's installed. Any idea why/ what it is? I have removed the aircraft and the message doesn't appear again.

Kind Regards

Dale, this looks like the issue which has been reported a few posts upstream (June 14/15). The FSX version of fx_dummy.fx seems to be the cause. Steve did provide a fix for the FSX fx_dummy.fx file:

https://app.box.com/s/336y5fcry58t81qstf3zuvpmdx0rl2vd

Henk.

Thank you for that, seems to have worked great.

That is indeed good news, Dale.
When Henk first raised the issue I thought I knew what might be causing the issue but not having FSX I couldn't test it. I needed people like yourself to prove it one way or another.

Yeah it works fine for me Steve. I didn't know about it until I asked the question. I also got it with the F/A-18C too, I've not tried it with them yet.

Dale, if you installed the FSX fx_dummy.fx fix for the the NBAI Hawks, it should also fix the NBAI Hornets visual.fx crashes, no need to do anything extra.

Henk.

Oh yeah I understand that, I just haven't looked at the hornets since I've added the file. Could the file be uploaded to the library in case others get the same issue?

The plan was that Henk would indeed make it available once we knew that it fixed the issue.

The download link for the updated T2 model is dead

Rick

Rick, somehow I must have deleted them... They are not on my physical drives either.

Sorry, Henk.