-
Please see the most recent updates in the "Where did the .com name go?" thread. Posts number 16 and 17.
Error Message
- Thread starter DaleRFU
- Start date
blanston12
SOH-CM-2025
I did a quick search and found this.
https://support.microsoft.com/en-us/help/125749/description-of-the-r6025-run-time-error-in-visual-c
But the bottom line is a programming error in the application you were running, what were you doing when this error happened?
https://support.microsoft.com/en-us/help/125749/description-of-the-r6025-run-time-error-in-visual-c
But the bottom line is a programming error in the application you were running, what were you doing when this error happened?
hschuit
SOH-CM-2026
Dale, I just answered the same question you posted on MAIW: 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
The full story is on the MAIW support forum.
Henk.
https://app.box.com/s/336y5fcry58t81qstf3zuvpmdx0rl2vd
The full story is on the MAIW support forum.
Henk.
spokes2112
Charter Member
More info Henk?
Henk,
Do you happen to have the link to the specific forum post?
Used search with multiple queries with no results.
Would like to read more about their findings.
This bug has been a pain since FSX came out,
especially during the RTWR where a certain popular
plane causes this during multiplayer sessions,
ruining official race legs.
It propagates across a multiplayer network! UGGH!
We did know it was effect related but couldn't pinpoint.
Looked at the replacement .fx you linked (THANKS!),
WOW -- it is much different!
Don't understand why 3 complete element sets are used
when 1 is enough & why there's a Z (or Y? dont recall now)
offset.. Will look into it more when time allows and more info is found.
Thanks alot!
Roman
Henk,
Do you happen to have the link to the specific forum post?
Used search with multiple queries with no results.
Would like to read more about their findings.
This bug has been a pain since FSX came out,
especially during the RTWR where a certain popular
plane causes this during multiplayer sessions,
ruining official race legs.
It propagates across a multiplayer network! UGGH!
We did know it was effect related but couldn't pinpoint.
Looked at the replacement .fx you linked (THANKS!),
WOW -- it is much different!
Don't understand why 3 complete element sets are used
when 1 is enough & why there's a Z (or Y? dont recall now)
offset.. Will look into it more when time allows and more info is found.
Thanks alot!
Roman
hschuit
SOH-CM-2026
Roman, here is the link to the conversation on the MAIW forum. Please note that fx_dummy.fx is not the only FX file causing visualfx.dll C runtime crashes in FSX. In the past I have found several afterburner FX files doing the same thing. Interestingly, in the case of the MAIW Hawk and F/A-18 Hornet AI FSX/P3D conversions, less than 5 people out of almost 2,000 downloaders reported this issue. I predominantly use P3Dv4 these days and I have not yet seen this problem there.
Henk.
Henk.
spokes2112
Charter Member
Thank You very much Henk.. 
Same observations too! It only affects a few of us.
We did nail it down to the Piaggio Avanti (free), low and behold, in the aircraft.cfg are multiple calls for the dummy within the [lights] section.
I assume the dummy was used to provide current draw when the light is is on while using a 3D modelled light.
That's how it works -> no effect = no current draw in the light section.
Same observations too! It only affects a few of us.
We did nail it down to the Piaggio Avanti (free), low and behold, in the aircraft.cfg are multiple calls for the dummy within the [lights] section.
I assume the dummy was used to provide current draw when the light is is on while using a 3D modelled light.
That's how it works -> no effect = no current draw in the light section.
hschuit
SOH-CM-2026
That is the same reason I used fx_dummy.fx for the FSX/P3D NBAI Hawk and Hornets. For beacon (type 1) / strobe (type 2) lights to work, the sim requires at least one [lights] nav light entry (type 3). Nowadays I do not use fx_dummy.fx anymore, instead I assign beacon/strobe light effects to type 7 (recognition).