Magma The Fallen Levels Bug Report

Talk about anything here.
Post Reply
fildred13
Posts: 162
Joined: Wed Jun 03, 2009 2:03 pm
Location: Boston, MA
Contact:

Magma The Fallen Levels Bug Report

Post by fildred13 »

Searched through the forums, couldn't find any mention of this elsewhere.

Issue:

Launching "A Vivid Thrashing" from the Magma TFL Multipack results in instant Crash To Desktop

Tested on:

Two different Windows 10 machines
Running Myth 1.8.1

Relevant part of myth log:

Code: Select all

Starting mesh "A Vivid Thrashing" with 2 plugins...
	Magma TFL Multipack
	Patch 1.5 Unity
Using 1.8.1 gameplay...
Error: Data Corrupted in Myth2Code\map_actions\map_actions.c, line #1869: invalid map action parameter type #25859 is not in (#0, #20)
Quitting networked game...
I'm not clear if this is an issue with Myth itself, or an issue with the map Using some non-backwards compatible map action (which I did not think the new patches were supposed to create). If it's an issue with the map, I'll be happy to submit a patch. If it's an issue with the app itself ... well I never did get accepted to help work on Myth's source code yet :). Maybe a good first assignment? Eh? Eh?
Gaming Rig: $2000
Apple Cinema Display:$1000
Using for 90% mything: priceless
hmp
Posts: 146
Joined: Fri Dec 14, 2007 3:00 am

Re: Magma The Fallen Levels Bug Report

Post by hmp »

Get same crash, also there does not appear to be any scripting on the map, so that's even stranger.
Myrd
Site Admin
Posts: 4031
Joined: Fri Mar 19, 2004 10:17 pm

Re: Magma The Fallen Levels Bug Report

Post by Myrd »

Interesting. Looks like this stopped working with 1.8. Specifically, Build 401 was the first version where this map would no longer load. Will look into it.
Myrd
Site Admin
Posts: 4031
Joined: Fri Mar 19, 2004 10:17 pm

Re: Magma The Fallen Levels Bug Report

Post by Myrd »

Looking at the relevant code, what happened is we added stricter validation to map action parameters in 1.8. This specific map has some bad data in its map action parameter buffer. Even though there's no map actions, there are parameters encoded in the mesh - which unfortunately have invalid/corrupted data. So the fix would be to resave that mesh in a way that doesn't preserve the bad data (not sure if Loathing will do this automatically or whether some tweaking is needed.)
Post Reply