Jump to content

Recommended Posts

Posted

After the most recent patch I am finding issues placing a P51 on the map in the mission editor. All mods disabled, repair has been run, P51 module deactivated uninstalled and reinstalled. The issue I am seeing is that selecting a P51 and trying to place the unit on the map results in no icon being displayed and the unit waypoint properties dialog getting corrupted with labels overwriting them selves. I am then unable to exit the me and am forced to use task manager to end DCS.exe. Other modules seem ok so far in regard to placing them on the map although I have not yet had time to create a simple mission and run it (it's very late here and I had really only planned to fire up DCS and fly for a sec to see what it went like after the patch before going to bed).

 

I checked the logs and found the errors shown below, anyone else seeing something similar?

 

Thanks,

Stonehouse

 

00053.426 ALERT LUACOMMON: Error: GUI Error: [string "./MissionEditor/modules/loadLiveries.lua"]:85: bad argument #1 to 'loadstring' (string expected, got nil)

GUI debug.traceback: stack traceback:

[C]: ?

[C]: in function 'loadstring'

[string "./MissionEditor/modules/loadLiveries.lua"]:85: in function 'loadLiveryZIP'

[string "./MissionEditor/modules/loadLiveries.lua"]:120: in function 'loadNameScheme'

[string "./MissionEditor/modules/loadLiveries.lua"]:131: in function 'loadSchemes'

[string "./MissionEditor/modules/me_payload.lua"]:468: in function 'setDefaultLivery'

[string "./MissionEditor/modules/me_mission.lua"]:3549: in function 'insert_unit'

[string "./MissionEditor/modules/me_map_window.lua"]:3269: in function 'createAircraft'

[string "./MissionEditor/modules/me_map_window.lua"]:1640: in function 'onMouseDown'

[string "./dxgui/bind/NewMapView.lua"]:359: in function 'callback'

[string "./dxgui/bind/Widget.lua"]:242: in function <[string "./dxgui/bind/Widget.lua"]:241>

00062.473 WARNING LOG: 2 duplicate message(s) skipped.

00062.473 ALERT LUACOMMON: Error: GUI Error: [string "./MissionEditor/modules/me_aircraft.lua"]:635: attempt to index field '?' (a nil value)

GUI debug.traceback: stack traceback:

[C]: ?

[string "./MissionEditor/modules/me_aircraft.lua"]:635: in function 'changeType'

[string "./MissionEditor/modules/me_aircraft.lua"]:2087: in function 'onChange'

[string "./dxgui/bind/ComboList.lua"]:21: in function 'callback'

[string "./dxgui/bind/Widget.lua"]:311: in function <[string "./dxgui/bind/Widget.lua"]:306>

00089.319 ALERT LUACOMMON: Error: GUI Error: [string "./MissionEditor/modules/loadLiveries.lua"]:85: bad argument #1 to 'loadstring' (string expected, got nil)

GUI debug.traceback: stack traceback:

[C]: ?

[C]: in function 'loadstring'

[string "./MissionEditor/modules/loadLiveries.lua"]:85: in function 'loadLiveryZIP'

[string "./MissionEditor/modules/loadLiveries.lua"]:120: in function 'loadNameScheme'

[string "./MissionEditor/modules/loadLiveries.lua"]:131: in function 'loadSchemes'

[string "./MissionEditor/modules/me_payload.lua"]:468: in function 'setDefaultLivery'

[string "./MissionEditor/modules/me_mission.lua"]:3549: in function 'insert_unit'

[string "./MissionEditor/modules/me_map_window.lua"]:3269: in function 'createAircraft'

[string "./MissionEditor/modules/me_map_window.lua"]:1640: in function 'onMouseDown'

[string "./dxgui/bind/NewMapView.lua"]:359: in function 'callback'

[string "./dxgui/bind/Widget.lua"]:242: in function <[string "./dxgui/bind/Widget.lua"]:241>

Posted (edited)

Not 100% sure but since it is now working it would seem fair to think I have found the root cause. It looks like the functionality of loadlivery.lua (Mission editor folder) changed to now include the ability to use zipped skin files. I had a partly completed skin in a zip file in the root of Bazar\liveries\P-51D and it looks like loadlivery was unzipping the file and parsing the description.lua file - which had a table handling error - causing the mission editor to not be able to place a F icon for the P51 and causing corruption to the unit properties dialog. Deleting the zipfile immediately fixed the problem.

Edited by Stonehouse
  • Recently Browsing   0 members

    • No registered users viewing this page.
×
×
  • Create New...