Recent Posts

Pages: 1 [2] 3 4 ... 10
11
SCI Syntax Help / Re: Status line vertical size
« Last post by MusicallyInspired on May 26, 2021, 08:53:15 PM »
I remember fiddling with setport but for some reason I thought some of this stuff was hardcoded or at least predisposed to be set up that way, seeing as all Pictures are a set height.
12
SCI Syntax Help / Re: Status line vertical size
« Last post by gumby on May 26, 2021, 07:40:11 PM »
I think another way to do it would be to use the SetPort kernel call.  I found examples of this when digging around in the TitleScreen.sc.
13
I may have brought this up before, I don't remember. I discovered while streaming today that Companion doesn't seem to have the ability to alter channel properties on Dound resources. Mainly the "Initial Voices" value. This is important for Adlib because if it's not set no notes will be played at all. Ravi's SoundBox program can set this but it's only compatible with SCI0 Sound resources, which makes it unhelpful for SCI1+ games.

What the Initial Voices value does is set the polyphony limit for the channel it's set on. I think Adlib has a maximum limit of 8 voices across all Adlib channels total. I think some stereo OPL drivers (sndblast?) ignore this and have a higher polyphony limit but I'd like to be able to to support the original mono adl.drv driver too.

Unless Companion already supports this and I've missed it lol. The source for SoundBox is freely available so I'm going to take a look at it later tonight too.
14
SCI Syntax Help / Re: Status line vertical size
« Last post by MusicallyInspired on May 25, 2021, 07:04:12 PM »
Oh nice. I was wondering if this was possible.
15
SCI Syntax Help / Re: Status line vertical size
« Last post by gumby on May 25, 2021, 06:43:31 PM »
I got it figured out.  Just needed to trigger another call to update the status line code during the init of the room, after the picture is drawn.

EDIT: Better still, I just threw it in as the last line of the drawPic method in the room class.
16
SCI Syntax Help / Status line vertical size
« Last post by gumby on May 25, 2021, 09:51:19 AM »
I'm trying to get the status line to be a few pixels taller, the font I'm using has some characters that drop below the status line and get chopped off.  I was able to get the status line code modified to be larger, but when DrawPic commands are executed, they look to be getting applied at a y=10 and effectively overwriting the status line pixels that extend the 10th y pixel.

Anyone know if making a larger status line is possible?
18
Amazing feat Zvika! Congratulations!
19
AGI Syntax Help / Re: Need help adding text to parser
« Last post by Kawa on May 21, 2021, 12:26:56 PM »
@Kawa, btw, in your image the input box has the caption "Enter input" not "ENTER COMMAND". I assume that screen shot is from SCUMMVM then? Because in all the MSDOS versions I have, the caption is "ENTER COMMAND".
You assumed correctly. But in the end it doesn't really matter to the bigger point, does it?
20
AGI Syntax Help / Re: Need help adding text to parser
« Last post by AGKorson on May 21, 2021, 11:29:53 AM »
To be clear, in MSDOS, running on a monochrome monitor, AGI completely ignores the input prompt (i.e. it doesn't matter what you set string s0 to). The input box is hard coded to include the phrase "ENTER COMMAND" centered at the top of the box, with  the single input line that displays only the input text and the cursor just below. No input prompt is included, but you can change the cursor character (using set.cursor.char).

The buffer for the input text is in the same location as for any other video mode, but it is just as inaccessible. So you can't modify it through code, in HGC mode, or any other mode*.

@Kawa, btw, in your image the input box has the caption "Enter input" not "ENTER COMMAND". I assume that screen shot is from SCUMMVM then? Because in all the MSDOS versions I have, the caption is "ENTER COMMAND".

I don't know a lot about SCUMMVM, but my experience has been that the modern interpreters don't accurately capture all the nuances of the original DOS interpreter, because errors and edge cases tend to be ignored in modern systems (they don't let you overrun memory, for example). So there are things you can do in MSDOS (or using DOSBox) that modern interpreters just can't handle.

*I have a 'secret project' that I'm just about ready to release that will demonstrate some of the cool things you can do with the original DOS interpreter by taking advantage of some of their poor coding practices in AGI. (Spoiler: the functionality that klownstein is looking for is easily doable if you know the secret!)





Pages: 1 [2] 3 4 ... 10

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

Page created in 0.098 seconds with 17 queries.