1
SCI Development Tools / Re: SSCI, ScummVM, and polygons
« Last post by lskovlun on Today at 06:28:17 PM »Ask the man himself?
Recent Posts
2
SCI Development Tools / SSCI, ScummVM, and polygons
« Last post by Kawa on Today at 05:39:59 PM »Some two hours ago, another commit was made to ScummVM involving differences between its pathfinder and Sierra's. In this case, it involved SQ6 and a spike shape in one of the rooms' polygons which is removed by a script patch. Another commit fixes a barred-access poly that extends beyond a contained-access poly which trips up the logic. I've seen patches like this before where a problematic polygon shape needs to be tweaked (LB2 comes to mind, not sure if correctly) and now I have to wonder.
What exactly are the problematic shapes that ScummVM's pathfinder has trouble with? Knowing what to avoid and how could help home-made SCI games run correctly on both interpreters.
What exactly are the problematic shapes that ScummVM's pathfinder has trouble with? Knowing what to avoid and how could help home-made SCI games run correctly on both interpreters.
3
SCI Development Tools / Re: Looping Audio in SCI1.1?
« Last post by Collector on April 28, 2026, 07:38:49 PM »in LB2 most songs are MIDI, but "The Archaeologist Song" has both a MIDI version and an audio version with lyrics. So you can call the MIDI version with 312 or the digital version with 1312.
As in KQ5 where The Weeping Willow song has both.
4
SCI Development Tools / Re: Looping Audio in SCI1.1?
« Last post by lskovlun on April 28, 2026, 07:04:07 PM »Yeah, that's what one game does. But there is code in the interpreter to make sure that it generally doesn't matter whether a sound resource is MIDI or Wave.
5
SCI Development Tools / Re: Looping Audio in SCI1.1?
« Last post by doomlazer on April 28, 2026, 06:57:22 PM »(using unused numbers, as Sound and Audio assets share a namespace).
I believe that despite seeming to share the same resource numbers you can differentiate between sound and audio by prepending a 1 before the number to use digital audio.
For example, in LB2 most songs are MIDI, but "The Archaeologist Song" has both a MIDI version and an audio version with lyrics. So you can call the MIDI version with 312 or the digital version with 1312.
6
SCI Development Tools / Re: Looping Audio in SCI1.1?
« Last post by cdb-boop on April 25, 2026, 08:20:08 PM »Never mind. I realized you can just call an Audio resource with DoSound and loop with -1 infinitely.
7
SCI Development Tools / Looping Audio in SCI1.1?
« Last post by cdb-boop on April 25, 2026, 06:25:00 PM »I'm porting a SCI1 game to the SCI Companion's SCI1.1 template game and some of the SCI1 Sound assets have a digital track embedded. I used Sierra Resource Viewer to extract all the digital tracks as WAV files and add them as Audio resources (using unused numbers, as Sound and Audio assets share a namespace).
I have been auditing the code's 374 play: calls and making modifications to affected sounds. For example, using (DoSound sndGET_AUDIO_CAPABILITY) to dynamically swap between using Sound and Audio asset depending on audio driver. I also ended up creating a DigitalSound wrapper class to emulate cases of dynamically setting a Sound object's number property for play later.
So far I've found two cases (battle yelling and tavern chatter) where a Sound with a digital track is looped for ambiance. I looked at the SCI Companion Docs but I didn't see a way to loop DoAudio in SCI1.1. Is there a built-in way to loop Audio, like setting the Sound class's loop property to -1? I was wondering if it was possible to attach a script to a room's script to detect when it was time to loop the audio, or make a global list like gSounds or global object like gMusic and add check in the main game loop. Or should I just use gumby's sciAudio which supports looping but is not "authentic"?
Is there a best or intended way to loop Audio in SCI1.1?
I have been auditing the code's 374 play: calls and making modifications to affected sounds. For example, using (DoSound sndGET_AUDIO_CAPABILITY) to dynamically swap between using Sound and Audio asset depending on audio driver. I also ended up creating a DigitalSound wrapper class to emulate cases of dynamically setting a Sound object's number property for play later.
So far I've found two cases (battle yelling and tavern chatter) where a Sound with a digital track is looped for ambiance. I looked at the SCI Companion Docs but I didn't see a way to loop DoAudio in SCI1.1. Is there a built-in way to loop Audio, like setting the Sound class's loop property to -1? I was wondering if it was possible to attach a script to a room's script to detect when it was time to loop the audio, or make a global list like gSounds or global object like gMusic and add check in the main game loop. Or should I just use gumby's sciAudio which supports looping but is not "authentic"?
Is there a best or intended way to loop Audio in SCI1.1?
8
SCI Development Tools / Re: Converting Pics from SCI1 to SCI1.1 format
« Last post by cdb-boop on April 15, 2026, 10:22:43 PM »Thanks! I see now! 64 globally and the rest for the room. I'll have to reconvert the Pics because they have the wrong global palette embedded. And I can use the palette remap feature to align actors with the global palette.
9
SCI Development Tools / Re: Converting Pics from SCI1 to SCI1.1 format
« Last post by Kawa on April 15, 2026, 11:00:22 AM »I believe it's also the reason most actors keep to the first 16 (or 32) colors so they can move between all rooms without issue. The rest of the colors are then used for pics or per room objects.The global palette tends to be 64 colors (0-63, plus 255). Other than that you're basically on the money.
10
SCI Development Tools / Re: Converting Pics from SCI1 to SCI1.1 format
« Last post by doomlazer on April 15, 2026, 10:33:40 AM »Isn't that the expected behavior? There should only be one palette available per room. Loading a pic and view with conflicting palettes is going to overwrite the previous colors.
That's why you can't transition between rooms with conflicting palettes without distortion or fading to black. This was often the case with EcoQuest where they would use checkerboard transitions between rooms with incompatible palettes and it looked terrible.
I believe it's also the reason most actors keep to the first 16 (or 32) colors so they can move between all rooms without issue. The rest of the colors are then used for pics or per room objects.
As an aside, with scummvm you can do some palette tricks, like overriding the static SCI0 palette. You're still limited to 16 colors, but you can assign them to any RGB value, allowing for a monochromatic effect with a dozen shades of a single color.
That's why you can't transition between rooms with conflicting palettes without distortion or fading to black. This was often the case with EcoQuest where they would use checkerboard transitions between rooms with incompatible palettes and it looked terrible.
I believe it's also the reason most actors keep to the first 16 (or 32) colors so they can move between all rooms without issue. The rest of the colors are then used for pics or per room objects.
As an aside, with scummvm you can do some palette tricks, like overriding the static SCI0 palette. You're still limited to 16 colors, but you can assign them to any RGB value, allowing for a monochromatic effect with a dozen shades of a single color.
SMF 2.0.19 |
SMF © 2021, Simple Machines
Simple Audio Video Embedder
Page created in 0.045 seconds with 16 queries.