Sign in to follow this  
spokes2112

Possible fix F-7F R6025 virtual call error

Recommended Posts

RTWR_2013_020.jpg

 

 

Notice in the [light] section, aircraft.cfg (this applies to all GMAN F-7Fs) that the numbering is out of order, skipping 3-7.

[lights]
//Types: 1=beacon, 2=strobe, 3=navigation, 4=cockpit, 5=landing
light.0 = 4, 3.64, 0, 1.99, Fx_shockwave_vclight,
light.1 = 3, -29.27, 0, -0.65, Fx_shockwave_beaconb, // renamed from "Fx_shockwave_beacon_b" which was not found
light.2 = 4, -10.64, 0, 1.99, Fx_shockwave_vclight,
//light.4 =5, 8.3, -19.8, -2.8, Fx_landing,
light.8 = 9, -3.70, 7.700, -1.250, fx_msf7f_start,
light.9 = 9, -3.70, -7.700, -1.250, fx_msf7f_start,
//light.10 = 8, -3.70, 7.700, -1.250, fx_f7f_airstart,
//light.11 = 8, -3.70, -7.700, -1.250, fx_f7f_airstart,
I modded all tigercats so it looks like the following including removing all trailing commas -

[lights]
//Types: 1=beacon, 2=strobe, 3=navigation, 4=cockpit, 5=landing
light.0 = 4, 3.64, 0, 1.99, Fx_shockwave_vclight
light.1 = 3, -29.27, 0, -0.65, Fx_shockwave_beaconb // renamed from "Fx_shockwave_beacon_b" which was not found
light.2 = 4, -10.64, 0, 1.99, Fx_shockwave_vclight
light.3 = 9, -3.70, 7.700, -1.250, fx_msf7f_start
light.4 = 9, -3.70, -7.700, -1.250, fx_msf7f_start
 
Also just to be safe commented out these -

//[smokesystem] Whole header commented out as no entries will be used
//smoke.0 = -18,  9.70, -0.400, fx_contrail_l
//smoke.1 = -18, -9.70, -0.400, fx_contrail_l
The virtual call error was triggered when the following aircraft was trying to be loaded by JoinFS - 

2/18/2017 12:52:49 PM Added plane: G-142, F7F-3s Single Seat Marines, as F7F-3s Single Seat Armed
2/18/2017 12:52:49 PM Added plane: , F7F-3S Jaded Dragon, as F7F-3s Single Seat Metal
2/18/2017 12:53:24 PM Simconnect exception: 3
2/18/2017 12:53:53 PM Added plane: S5250X, F7F-3s Single Seat Metal, as F7F-3s Single Seat Metal
2/18/2017 12:54:15 PM Exception from HRESULT: 0xC000014B
And the resulting .dll thrown by FS -

Faulting application name: fsx.exe, version: 10.0.61637.0, time stamp: 0x46fadb14
Faulting module name: visualfx.dll, version: 10.0.61637.0, time stamp: 0x46fadb59
Exception code: 0x40000015
Fault offset: 0x000048a9
Faulting process id: 0xfd8
Faulting application start time: 0x01d28a17a5c2d75f
Faulting application path: G:\FSX\fsx.exe
Faulting module path: G:\FSX\visualfx.dll
Report Id: 9e7b803b-f60b-11e6-b117-20cf30e43ebc

Share this post


Link to post
Share on other sites
Help AVSIM continue to serve you!
Please donate today!

It has bitten again....
A test procedure has been hypothesised using JoinFS (recordings) so I can do it locally.
Not on the top of the list, but hopefully soon, a "remedy to this horrible affliction" will be had.

 

Share this post


Link to post
Share on other sites

Create an account or sign in to comment

You need to be a member in order to leave a comment

Create an account

Sign up for a new account in our community. It's easy!

Register a new account

Sign in

Already have an account? Sign in here.

Sign In Now
Sign in to follow this