Author Topic: Maxium possible global variables / Status bar corruption?  (Read 590 times)

0 Members and 1 Guest are viewing this topic.

Offline gumby

Re: Maxium possible global variables / Status bar corruption?
« Reply #15 on: March 25, 2018, 05:49:33 PM »
Thanks for the new build, appreciate it.
In the Great Underground Empire (Zork port in development)
Winter Break 2012 Rope Prop Competition

Offline troflip

Re: Maxium possible global variables / Status bar corruption?
« Reply #16 on: March 25, 2018, 09:02:35 PM »
Workaround no-workie.  I tried various flavors of no-ops, couldn't get it to clear the issue.  I'll try a build next.

[Edit]:  Correction, I was able to clear the issue.  'Initializing' the string works perfectly:

Code: [Select]
    (StrCpy @temp50 "")
(Format @temp50 {%s %d} @temp0 gScore)

Which is strange because I vaguely remember doing this before in other circumstances, probably for the same reason (SCI0 games).  This may be a really, really old bug going back to Companion 2?

Couldn't be, because it doesn't happen in SCI0: it only happens for games that use separate .scr and .hep resources. It will occur when the code offset of the lofsa/lofss instruction (which loads a string/instance/said pointer into the accumulator) in the .scr resource is the exact same number as the offset of a string for a class property value in the .hep resource.

When that happens, the wrong string pointer can get compiled into the code. So adding some more code before the offending string will cause the code offset to change (and likely the bug to go away, until it lines up with something else).

So in your case, the place that referenced the {%s %d} string ptr was at offset 2353 (for example) in the .scr resource, and the name property value for the lb2FtrInit instance was at offset 2353 in the .hep resource.

« Last Edit: March 25, 2018, 09:04:42 PM by troflip »
Check out my website: http://icefallgames.com
Groundhog Day Competition

Offline MusicallyInspired

Re: Maxium possible global variables / Status bar corruption?
« Reply #17 on: March 27, 2018, 09:15:51 PM »
Can someone send me a build? lol
Shure mate. Trade you for a full GM 1.pat? ;)

Lol touche.

Seriously, though. The problem, the reason I've been avoiding it, is because not all of the instruments I need for a full GM patch exist in the vast library of MT-32 timbres I have. I'd need to make some from scratch and I just don't know where to begin doing that. I've been toying with just finding alternate timbres that sound close, but I don't want to do a cheap hack or be too far off-base.
Brass Lantern Prop Competition


SMF 2.0.14 | SMF © 2017, Simple Machines
Simple Audio Video Embedder

Page created in 0.127 seconds with 23 queries.