2.5 openbeta old 1.5 and 2.2 missions not allowing picking

[robgraham]

So updated to 2.5 and opened a 1.5.8 mission and a 2.2 mission in the ME and when to move a zone only to find nothing happened at all.

 

So I checked the log

2018-02-01 06:29:28.193 ALERT   LUACOMMON: Error: GUI Error: [string "./MissionEditor/modules/me_map_window.lua"]:793: attempt to index field 'userObject' (a nil value)
GUI debug.traceback: stack traceback:
[C]: ?
[string "./MissionEditor/modules/me_map_window.lua"]:793: in function 'pickUserObject'
[string "./MissionEditor/modules/me_map_window.lua"]:1584: in function 'handleLeftMouseDown'
[string "./MissionEditor/modules/me_map_window.lua"]:1696: in function 'onMouseDown'
[string "./dxgui/bind/NewMapView.lua"]:373: in function 'callback'
[string "./dxgui/bind/Widget.lua"]:261: in function <[string "./dxgui/bind/Widget.lua"]:260>
2018-02-01 06:29:28.268 ALERT   LUACOMMON: Error: GUI Error: [string "./MissionEditor/modules/me_map_window.lua"]:793: attempt to index field 'userObject' (a nil value)
GUI debug.traceback: stack traceback:
[C]: ?
[string "./MissionEditor/modules/me_map_window.lua"]:793: in function 'pickUserObject'
[string "./MissionEditor/modules/me_map_window.lua"]:1584: in function 'handleLeftMouseDown'
[string "./MissionEditor/modules/me_map_window.lua"]:1251: in function 'onMouseUp'
[string "./dxgui/bind/NewMapView.lua"]:398: in function 'callback'
[string "./dxgui/bind/Widget.lua"]:261: in function <[string "./dxgui/bind/Widget.lua"]:260>

 

This is only happening on OLD missions though if I create a mission from scratch no issue. Great example is Georgia Cap Cas infinity you open it and try and move the zone and i get that happening (was trying to reposition it given the changes on the map now).

[USSR_Rik]

Please attach any mission.

[robgraham]

Rik here you go, I was doing some testing it seems very hit and miss some of my missions are loading in fine others are having that error.. and i can not find a 'common' between them except perhaps it being maybe a user unit that is causing the issue.

 

and weirdly.. however IF I go into the Mission Briefing, type something into the window there.. then go click something everything pick's fine....

CASCAP_Infinity_Georgia_West_1.65-modified.zip

Edited February 1, 2018 by robgraham

[robgraham]

I'll try and get a video of what is happening as well Rik if that helps?

[robgraham]

Rik this shows the bug and reproducing it and well.. the work around for fixing it... everything else seems to be working fine etc.

 

 

 

addition: however even after a save reopening will cause the same issue.. and the Mission Editor file menu doens't appear to refresh properly either.

[Grimes]

Appears to be caused by dynamic weather and the overlay it creates. Switch the weather system to static and you should be able to select the trigger zone. If you set it back to dynamic then the error is created and nothing happens when you click.

 

Try that out on your end to see if the same behavior occurs.

[robgraham]

Appears to be caused by dynamic weather and the overlay it creates. Switch the weather system to static and you should be able to select the trigger zone. If you set it back to dynamic then the error is created and nothing happens when you click.

 

Try that out on your end to see if the same behavior occurs.

 

 

Grimes: yeah appears to be so long as you do anything that kills the 'Grey' overlay the picking works again correctly (Briefing, Kill Dynamic etc etc) but if you don't.. then it errors out and snows balls seemingly into other GUI errors (File Menu not updating correctly after saving a mission with a new name (it doesn't show up at all)) etc.

[USSR_Rik]

Thanks, reproduced.

[robgraham]

Just incase it was meant to have been fixed in the last patch.. this is still happening as of build : DCS/2.5.0.14044 (x86_64; Windows NT 10.0.16299)

[Grimes]

Nope, bug is still open.

[robgraham]

yay fixed thanks :D no more having to remember to switch to breifing or to kill dynamics