|
Post by dca309president on Jun 22, 2019 15:21:17 GMT
Since the latest X-Plane 11 update, every time I load the DC-3, I get an error message that reads, "There was a minor problem loading the aircraft: Aircraft/VSKYLABS DC-3 C-47 Flying Lab Project AU/VSL DC-3.acf" The only suggestion the message gives me is to contact the vendor for an update. This morning, I loaded the aircraft and let it update, then reloaded the aircraft after the update was complete, yet the error message still appears. I am open to any suggestions...
|
|
|
Post by VSL-Admin on Jun 22, 2019 15:29:25 GMT
Since the latest X-Plane 11 update, every time I load the DC-3, I get an error message that reads, "There was a minor problem loading the aircraft: Aircraft/VSKYLABS DC-3 C-47 Flying Lab Project AU/VSL DC-3.acf" The only suggestion the message gives me is to contact the vendor for an update. This morning, I loaded the aircraft and let it update, then reloaded the aircraft after the update was complete, yet the error message still appears. I am open to any suggestions... Hi there! Please specify exact X-Plane version, and if you are experiencing any issues in addition to this message. Thanks!
|
|
|
Post by dca309president on Jun 22, 2019 20:48:49 GMT
Thanks for the quick reply. I am on 11.34r1. I haven't noticed anything, but I haven't flown it since the error message appeared. I did look in the log.txt file and here's what I found;
Failed to open Aircraft/VSKYLABS DC-3 C-47 Flying Lab Project AU/objects/ENGINES-B-SPINNERS.obj: the file cannot be opened. 0:00:16.116 E/ACF: Error with aircraft: Aircraft/VSKYLABS DC-3 C-47 Flying Lab Project AU/VSL DC-3.acf (C:\jenkins\design-triggered\source_code\engine\veh\read\veh_planes_read.cpp:2173) 0:00:16.116 E/ACF: X-Plane was unable to load the object file "Aircraft/VSKYLABS DC-3 C-47 Flying Lab Project AU/objects/ENGINES-B-SPINNERS.obj" that should be attached to this airplane. The file could be missing or unreadable. Failed to open Aircraft/VSKYLABS DC-3 C-47 Flying Lab Project AU/objects/ENGINES-C-CORE.obj: the file cannot be opened. 0:00:16.116 E/ACF: Error with aircraft: Aircraft/VSKYLABS DC-3 C-47 Flying Lab Project AU/VSL DC-3.acf (C:\jenkins\design-triggered\source_code\engine\veh\read\veh_planes_read.cpp:2173) 0:00:16.116 E/ACF: X-Plane was unable to load the object file "Aircraft/VSKYLABS DC-3 C-47 Flying Lab Project AU/objects/ENGINES-C-CORE.obj" that should be attached to this airplane. The file could be missing or unreadable. 0:00:16.116 W/ACF: Aircraft/VSKYLABS DC-3 C-47 Flying Lab Project AU/fmod/VSL DC-3.snd:821: 0:00:16.116 W/ACF: Sound attachment marked to work with AI aircraft but sim/cockpit and sim/flightmodel datarefs only work for the user's aircraft. 0:00:16.116 I/SND: This aircraft is using FMOD in PARTIAL mode. 0:00:16.116 E/SOUN: snd error in file: Aircraft/VSKYLABS DC-3 C-47 Flying Lab Project AU/fmod/VSL DC-3.snd line 1003 0:00:16.116 E/SOUN: The sound attachment event:/gps is set to use a command-triggered hold cue but the FMOD event has no cue defined. 0:00:16.116 E/SOUN: snd error in file: Aircraft/VSKYLABS DC-3 C-47 Flying Lab Project AU/fmod/VSL DC-3.snd line 1009 0:00:16.116 E/SOUN: The sound attachment event:/gps is set to use a command-triggered hold cue but the FMOD event has no cue defined. 0:00:16.116 E/SOUN: snd error in file: Aircraft/VSKYLABS DC-3 C-47 Flying Lab Project AU/fmod/VSL DC-3.snd line 1015 0:00:16.116 E/SOUN: The sound attachment event:/gps is set to use a command-triggered hold cue but the FMOD event has no cue defined. 0:00:16.116 E/SOUN: snd error in file: Aircraft/VSKYLABS DC-3 C-47 Flying Lab Project AU/fmod/VSL DC-3.snd line 1021 0:00:16.116 E/SOUN: The sound attachment event:/beep is set to use a command-triggered hold cue but the FMOD event has no cue defined. 0:00:16.116 E/SOUN: snd error in file: Aircraft/VSKYLABS DC-3 C-47 Flying Lab Project AU/fmod/VSL DC-3.snd line 1027 0:00:16.116 E/SOUN: The sound attachment event:/gps is set to use a command-triggered hold cue but the FMOD event has no cue defined. 0:00:16.116 E/SOUN: snd error in file: Aircraft/VSKYLABS DC-3 C-47 Flying Lab Project AU/fmod/VSL DC-3.snd line 1033 0:00:16.116 E/SOUN: The sound attachment event:/gps is set to use a command-triggered hold cue but the FMOD event has no cue defined. 0:00:16.116 E/SOUN: snd error in file: Aircraft/VSKYLABS DC-3 C-47 Flying Lab Project AU/fmod/VSL DC-3.snd line 1039 0:00:16.116 E/SOUN: The sound attachment event:/gps is set to use a command-triggered hold cue but the FMOD event has no cue defined. 0:00:16.116 E/SOUN: snd error in file: Aircraft/VSKYLABS DC-3 C-47 Flying Lab Project AU/fmod/VSL DC-3.snd line 1045 0:00:16.116 E/SOUN: The sound attachment event:/gps is set to use a command-triggered hold cue but the FMOD event has no cue defined. 0:00:16.116 E/SOUN: snd error in file: Aircraft/VSKYLABS DC-3 C-47 Flying Lab Project AU/fmod/VSL DC-3.snd line 1051 0:00:16.116 E/SOUN: The sound attachment event:/gps is set to use a command-triggered hold cue but the FMOD event has no cue defined. 0:00:16.116 E/SOUN: snd error in file: Aircraft/VSKYLABS DC-3 C-47 Flying Lab Project AU/fmod/VSL DC-3.snd line 1057 0:00:16.116 E/SOUN: The sound attachment event:/gps is set to use a command-triggered hold cue but the FMOD event has no cue defined. 0:00:16.116 E/SOUN: snd error in file: Aircraft/VSKYLABS DC-3 C-47 Flying Lab Project AU/fmod/VSL DC-3.snd line 1063 0:00:16.116 E/SOUN: The sound attachment event:/gps is set to use a command-triggered hold cue but the FMOD event has no cue defined. 0:00:16.116 E/SOUN: snd error in file: Aircraft/VSKYLABS DC-3 C-47 Flying Lab Project AU/fmod/VSL DC-3.snd line 1069 0:00:16.116 E/SOUN: The sound attachment event:/gps is set to use a command-triggered hold cue but the FMOD event has no cue defined. 0:00:16.116 E/SOUN: snd error in file: Aircraft/VSKYLABS DC-3 C-47 Flying Lab Project AU/fmod/VSL DC-3.snd line 1075 0:00:16.116 E/SOUN: The sound attachment event:/gps is set to use a command-triggered hold cue but the FMOD event has no cue defined. 0:00:16.116 E/SOUN: snd error in file: Aircraft/VSKYLABS DC-3 C-47 Flying Lab Project AU/fmod/VSL DC-3.snd line 1081 0:00:16.116 E/SOUN: The sound attachment event:/gps is set to use a command-triggered hold cue but the FMOD event has no cue defined. 0:00:16.116 E/SOUN: snd error in file: Aircraft/VSKYLABS DC-3 C-47 Flying Lab Project AU/fmod/VSL DC-3.snd line 1087 0:00:16.116 E/SOUN: The sound attachment event:/gps is set to use a command-triggered hold cue but the FMOD event has no cue defined. 0:00:16.116 E/SOUN: snd error in file: Aircraft/VSKYLABS DC-3 C-47 Flying Lab Project AU/fmod/VSL DC-3.snd line 1093 0:00:16.116 E/SOUN: The sound attachment event:/gps is set to use a command-triggered hold cue but the FMOD event has no cue defined. 0:00:16.116 E/SOUN: snd error in file: Aircraft/VSKYLABS DC-3 C-47 Flying Lab Project AU/fmod/VSL DC-3.snd line 1165 0:00:16.116 E/SOUN: The sound attachment event:/gps is set to use a command-triggered hold cue but the FMOD event has no cue defined. 0:00:16.116 E/SOUN: snd error in file: Aircraft/VSKYLABS DC-3 C-47 Flying Lab Project AU/fmod/VSL DC-3.snd line 1171 0:00:16.116 E/SOUN: The sound attachment event:/gps is set to use a command-triggered hold cue but the FMOD event has no cue defined. 0:00:16.116 E/SOUN: snd error in file: Aircraft/VSKYLABS DC-3 C-47 Flying Lab Project AU/fmod/VSL DC-3.snd line 1177 0:00:16.116 E/SOUN: The sound attachment event:/gps is set to use a command-triggered hold cue but the FMOD event has no cue defined. 0:00:16.116 E/SOUN: snd error in file: Aircraft/VSKYLABS DC-3 C-47 Flying Lab Project AU/fmod/VSL DC-3.snd line 1183 0:00:16.116 E/SOUN: The sound attachment event:/gps is set to use a command-triggered hold cue but the FMOD event has no cue defined. 0:00:16.116 E/SOUN: snd error in file: Aircraft/VSKYLABS DC-3 C-47 Flying Lab Project AU/fmod/VSL DC-3.snd line 1189 0:00:16.116 E/SOUN: The sound attachment event:/gps is set to use a command-triggered hold cue but the FMOD event has no cue defined. 0:00:16.116 E/SOUN: snd error in file: Aircraft/VSKYLABS DC-3 C-47 Flying Lab Project AU/fmod/VSL DC-3.snd line 1195 0:00:16.116 E/SOUN: The sound attachment event:/gps is set to use a command-triggered hold cue but the FMOD event has no cue defined. 0:00:16.116 E/SOUN: snd error in file: Aircraft/VSKYLABS DC-3 C-47 Flying Lab Project AU/fmod/VSL DC-3.snd line 1201 0:00:16.116 E/SOUN: The sound attachment event:/gps is set to use a command-triggered hold cue but the FMOD event has no cue defined. 0:00:16.116 E/SOUN: snd error in file: Aircraft/VSKYLABS DC-3 C-47 Flying Lab Project AU/fmod/VSL DC-3.snd line 1207 0:00:16.116 E/SOUN: The sound attachment event:/gps is set to use a command-triggered hold cue but the FMOD event has no cue defined. 0:00:16.116 E/SOUN: snd error in file: Aircraft/VSKYLABS DC-3 C-47 Flying Lab Project AU/fmod/VSL DC-3.snd line 1213 0:00:16.116 E/SOUN: The sound attachment event:/gps is set to use a command-triggered hold cue but the FMOD event has no cue defined. 0:00:16.116 E/SOUN: snd error in file: Aircraft/VSKYLABS DC-3 C-47 Flying Lab Project AU/fmod/VSL DC-3.snd line 1219 0:00:16.116 E/SOUN: The sound attachment event:/gps is set to use a command-triggered hold cue but the FMOD event has no cue defined. 0:00:16.116 E/SOUN: snd error in file: Aircraft/VSKYLABS DC-3 C-47 Flying Lab Project AU/fmod/VSL DC-3.snd line 1225 0:00:16.116 E/SOUN: The sound attachment event:/gps is set to use a command-triggered hold cue but the FMOD event has no cue defined. 0:00:16.116 E/SOUN: snd error in file: Aircraft/VSKYLABS DC-3 C-47 Flying Lab Project AU/fmod/VSL DC-3.snd line 1231 0:00:16.116 E/SOUN: The sound attachment event:/gps is set to use a command-triggered hold cue but the FMOD event has no cue defined. 0:00:16.116 E/SOUN: snd error in file: Aircraft/VSKYLABS DC-3 C-47 Flying Lab Project AU/fmod/VSL DC-3.snd line 1237 0:00:16.116 E/SOUN: The sound attachment event:/gps is set to use a command-triggered hold cue but the FMOD event has no cue defined. 0:00:16.116 E/SOUN: snd error in file: Aircraft/VSKYLABS DC-3 C-47 Flying Lab Project AU/fmod/VSL DC-3.snd line 1243 0:00:16.116 E/SOUN: The sound attachment event:/gps is set to use a command-triggered hold cue but the FMOD event has no cue defined. 0:00:16.116 E/SOUN: snd error in file: Aircraft/VSKYLABS DC-3 C-47 Flying Lab Project AU/fmod/VSL DC-3.snd line 1249 0:00:16.116 E/SOUN: The sound attachment event:/gps is set to use a command-triggered hold cue but the FMOD event has no cue defined. 0:00:16.116 E/SOUN: snd error in file: Aircraft/VSKYLABS DC-3 C-47 Flying Lab Project AU/fmod/VSL DC-3.snd line 1255 0:00:16.116 E/SOUN: The sound attachment event:/gps is set to use a command-triggered hold cue but the FMOD event has no cue defined. G64: 24.352: Livery Changed:() Folder:(Aircraft/VSKYLABS DC-3 C-47 Flying Lab Project AU/) 0:00:16.116 I/FLT: Init dat_p0 type:loc_ram apt:MYSM start at:Gate 1 0:00:25.030 I/SCN: DSF load time: 18262 for file Custom Scenery/Global Airports/Earth nav data/+20-080/+23-077.dsf (0 tris, 0 skipped for 0.0 m^2) 0:00:25.030 I/SCN: DSF load time: 60460 for file Custom Scenery/Global Airports/Earth nav data/+20-080/+25-077.dsf (0 tris, 0 skipped for 0.0 m^2) 0:00:25.030 I/SCN: DSF load time: 422322 for file Global Scenery/X-Plane 11 Global Scenery/Earth nav data/+20-080/+23-077.dsf (10305 tris, 0 skipped for 0.0 m^2) 0:00:25.030 I/SCN: DSF load time: 450981 for file Global Scenery/X-Plane 11 Global Scenery/Earth nav data/+20-080/+23-075.dsf (10717 tris, 0 skipped for 0.0 m^2) 0:00:25.030 I/SCN: DSF load time: 410811 for file Global Scenery/X-Plane 11 Global Scenery/Earth nav data/+20-080/+25-077.dsf (16794 tris, 2 skipped for -0.2 m^2) 0:00:25.030 I/DSF: Warning for missing scenery file: +25-075 0:00:25.030 I/SCN: DSF load time: 39479 for file Global Scenery/X-Plane 11 Global Scenery/Earth nav data/+20-080/+23-074.dsf (3166 tris, 0 skipped for 0.0 m^2) 0:00:25.030 I/SCN: DSF load time: 62931 for file Custom Scenery/Global Airports/Earth nav data/+20-080/+23-076.dsf (0 tris, 0 skipped for 0.0 m^2) 0:00:25.030 I/SCN: DSF load time: 186419 for file Global Scenery/X-Plane 11 Global Scenery/Earth nav data/+20-080/+23-076.dsf (33896 tris, 0 skipped for 0.0 m^2) 0:00:25.030 I/DSF: Warning for missing scenery file: +25-074 0:00:25.030 I/DSF: Warning for missing scenery file: +25-076 0:00:25.030 I/DSF: Warning for missing scenery file: +24-074 0:00:25.030 I/SCN: DSF load time: 18640 for file Custom Scenery/Global Airports/Earth nav data/+20-080/+24-077.dsf (0 tris, 0 skipped for 0.0 m^2) 0:00:25.030 I/SCN: DSF load time: 40221 for file Custom Scenery/Global Airports/Earth nav data/+20-080/+24-075.dsf (0 tris, 0 skipped for 0.0 m^2) 0:00:25.030 I/SCN: DSF load time: 81554 for file Global Scenery/X-Plane 11 Global Scenery/Earth nav data/+20-080/+24-075.dsf (8222 tris, 0 skipped for 0.0 m^2) 0:00:25.030 I/SCN: DSF load time: 138392 for file Global Scenery/X-Plane 11 Global Scenery/Earth nav data/+20-080/+24-077.dsf (19542 tris, 0 skipped for 0.0 m^2) 0:00:25.030 I/SCN: DSF load time: 135599 for file Global Scenery/X-Plane 11 Global Scenery/Earth nav data/+20-080/+24-076.dsf (17666 tris, 0 skipped for 0.0 m^2) FlyWithLua: User switched to a new airport (or changed the plane). Script files have to be reloaded. FlyWithLua Info: Lua engine (re)started. LUA_RUN = 1, SDK_VERSION = 301, XPLANE_VERSION = 11340, XPLANE_LANGUAGE = English and XPLANE_HOSTID = 1 FlyWithLua Info: HID access initialized. FlyWithLua Info: FlyWithLua.ini full path C:\Users/Roy/Desktop/X-Plane 11/Resources/plugins/FlyWithLua/Internals/FlyWithLua.ini FlyWithLua Info: Discovered 22 HID devices. FlyWithLua Info: Initial assignments successfully saved. FlyWithLua Info: Load ini file. FlyWithLua Info: Searching for Lua script files FlyWithLua Info: Sorting Lua script files FlyWithLua Info: Start loading script file C:\Users/Roy/Desktop/X-Plane 11/Resources/plugins/FlyWithLua/Scripts/makeshadowsgr8again v2.lua FlyWithLua Info: Finished loading script file C:\Users/Roy/Desktop/X-Plane 11/Resources/plugins/FlyWithLua/Scripts/makeshadowsgr8again v2.lua FlyWithLua Info: All script files loaded successfully. FlyWithLua Info: Loading time for all scripts is 0.121 sec. 0:00:43.349 I/OVR: Reading VR conf file: Aircraft/VSKYLABS DC-3 C-47 Flying Lab Project AU/VSL DC-3_vrconfig.txt 0:00:43.349 W/VRCONFIG: Could not find vr config file: Aircraft/VSKYLABS DC-3 C-47 Flying Lab Project AU/VSL DC-3_vrconfig.txt 0:00:43.349 W/VRCONFIG: VR Config data file for Aircraft/VSKYLABS DC-3 C-47 Flying Lab Project AU/VSL DC-3_vrconfig.txt is not valid! 0:00:43.349 W/MANIPS: Could not find vr config file: Aircraft/VSKYLABS DC-3 C-47 Flying Lab Project AU/VSL DC-3_vrconfig.txt 0:00:43.349 W/MANIPS: VR Manips file for Aircraft/VSKYLABS DC-3 C-47 Flying Lab Project AU/VSL DC-3_vrconfig.txt is not valid! 0:00:43.349 E/ACF: There were problems loading the aircraft Aircraft/VSKYLABS DC-3 C-47 Flying Lab Project AU/VSL DC-3.acf. Search above this point in the log for the specific errors. I will now warn the user. 0:00:43.349 E/SYS: +------------------------------------------------------------------------------- 0:00:43.349 E/SYS: | There was a minor problem loading the aircraft: 0:00:43.349 E/SYS: | Aircraft/VSKYLABS DC-3 C-47 Flying Lab Project AU/VSL DC-3.acf 0:00:43.349 E/SYS: | You may need to update the airplane or report this to the aircraft’s author. 0:00:43.349 E/SYS: | Please see the Log.txt file for detailed error information. 0:00:43.349 E/SYS: | (init_pln.cpp:2176) 0:00:43.349 E/SYS: +-------------------------------------------------------------------------------
|
|
|
Post by VSL-Admin on Jun 22, 2019 21:17:55 GMT
Thanks for the quick reply. I am on 11.34r1. I haven't noticed anything, but I haven't flown it since the error message appeared. I did look in the log.txt file and here's what I found; +------------------------------------------------------------------------------- Hi! Ok... After looking at this log file: It seems that your aircraft version may not updated properly. I can see it clearly because the .acf file is trying to load a missing object. That object is missing because it was removed during the last update batch. The other issues are referring to fmod, this is also should not occure. I highly recommend you to do a fresh install of the C-47, from the most recent version build (v2.8.01) which can be found in your store account. ...or to make sure that the autoupdater is enabled. You should see that your latest version is 2.8.01 after loading the plane. Please let me know if you need further assistance or advice! Thanks!
|
|
|
Post by dca309president on Jun 23, 2019 14:16:33 GMT
Downloading and reinstalling the C-47 solved the problem. Thanks!
|
|