robgraham Posted March 2, 2019 Posted March 2, 2019 (edited) The last Open Beta has really messed up something in the scripting backend, stuff that was running perfectly fine for months is now full of this: [string "-- world events hook..."]:427: in function <[string "-- world events hook..."]:313>. 2019-03-02 14:34:45.507 ERROR DCS: Mission script error: : [string "C:\Users\root\AppData\Local\Temp\DCS.openbeta\/~mis000051C2.lua"]:978: Parameter #self missed 2019-03-02 14:34:45.507 ERROR Lua::Config: Call error world.onEvent:[string "-- world events hook..."]:427: Parameter #self missed stack traceback: [C]: ? [C]: in function 'getCategory' local function groupSpawned(event) -- dont need to add units spawned in at the start of the mission if mist is loaded in init line if event.id == world.event.S_EVENT_BIRTH and timer.getTime0() < timer.getAbsTime() then dbLog:info('unitSpawnEvent') --table.insert(tempSpawnedUnits,(event.initiator)) ------- -- New functionality below. ------- if Object.getCategory(event.initiator) == 1 and not Unit.getPlayerName(event.initiator) then -- simple player check, will need to later check to see if unit was spawned with a player in a flight the last line in this is what is erroring constantly (part of MIST) however that is a standard event call and as said this was working 100% prior to the latest open beta patch, I know that the patch notes mentioned fixing some scripting issues but in that case maybe they should have included exactly what was fixed and how it's had an affect on the scripting incase this is a case of new functions parameters being required or the like? Quick edit before I get the normal 'Well its a mist issue' no this isn't a MIST issue, this is happening on EVERY item that uses those initator calls.. even stock API items. It means that anything which relies on the events firing is not working full stop and is a major break. Edited March 2, 2019 by robgraham i7 13700k, 64gb DDR5, Warthog HOTAS, HP Reverb G2 VR, win 11, RTX 3070 TGW Dedicated Server Admin, Australian PVE/PVP gameplay. (taskgroupwarrior.info/2020)
FlightControl Posted March 3, 2019 Posted March 3, 2019 reported. happens in 2.5.4.28090. you´re right. that one needs a fix. [TABLE][sIGPIC][/sIGPIC]| Join MOOSE community on: DISCORD :thumbup: Website of the MOOSE LUA Framework. MOOSE framework Downloads. Check out Example Missions to try out and learn. MOOSE YouTube Channel for live demonstrations and tutorials. [/TABLE]
SNAFU Posted March 19, 2019 Posted March 19, 2019 Are the EVENTS working again in the latest Beta? [sIGPIC][/sIGPIC] Unsere Facebook-Seite
robgraham Posted March 19, 2019 Author Posted March 19, 2019 fixed but new bugs with other stuff now i7 13700k, 64gb DDR5, Warthog HOTAS, HP Reverb G2 VR, win 11, RTX 3070 TGW Dedicated Server Admin, Australian PVE/PVP gameplay. (taskgroupwarrior.info/2020)
Grimes Posted March 19, 2019 Posted March 19, 2019 Yeah it was at least partially fixed. Hit events are inconsistently returning the weapon in multiplayer though. The right man in the wrong place makes all the difference in the world. Current Projects: Grayflag Server, Scripting Wiki Useful Links: Mission Scripting Tools MIST-(GitHub) MIST-(Thread) SLMOD, Wiki wishlist, Mission Editing Wiki!, Mission Building Forum
FlightControl Posted March 19, 2019 Posted March 19, 2019 Grimes, pls also check if player names can be correctly retrieved. I posted in known scripting engine issues. [TABLE][sIGPIC][/sIGPIC]| Join MOOSE community on: DISCORD :thumbup: Website of the MOOSE LUA Framework. MOOSE framework Downloads. Check out Example Missions to try out and learn. MOOSE YouTube Channel for live demonstrations and tutorials. [/TABLE]
Recommended Posts