SCI Companion V3 - alpha build notes/bugs/feature requests

[Kawa]

Whoever wrote SCI Debugger, I guess.

[lskovlun]

Am I stupid for not being able to tell the difference (apart from the fact that the two images are cropped slightly differently)?

[Kawa]

Look at the tooth on the right.

[Charles]

Which is the correct one, a or b?

[Kawa]

It's B. That's what it would like running in SCIV.

If you look at the default palette in the previous version of SCI Companion, you'll see that for example light and dark green is A/B, as are the others in that row, but light and dark blue are B/A.

[cosmicr]

Ha, crazy stuff I wonder how he noticed it.

A side effect from this is that digital archaeologists will be able to tell whether screenshots are from original interpreters or scummvm/others in the future...

[Kawa]

For fun, in SV.exe (sha-256 C31D2EF87C120E2C2560A264CBD1607C97DFDB8A3D91734421A6D83A51014420 specifically), the default palette mistake is at offset A36C5. That 0x91 should be 0x19. In SV-CLI's Graphics.exe (sha-256 57F9D537C6D0DE8F16E45F4CB65234B356C3644C3F867763D1103F3B2479D604), the same change goes in offset 2AEF5.

[doomlazer]

I can't find the post were it's discussed, but a feature was added in SCICompanion that allowed you to import a SCI1 view into a SCI1.1 project, change a pixel, revert it, and save - This converted it to a fully functional SCI1.1 view.

I was recently told that many LSL5 views do not import into SCI1.1 when trying to do this. Instead they show as a single grey cel.

I verified that LSL5 view 107.v56 breaks when importing to KQVI and SQIV; LSL5 view 106.v56 works as it should. I spot checked several more LSL5 views and it was about 50/50 if they would import.

I tried replacing the pallet from a working view into 107, but that didn't help. I also tried deleting view 107s loops one at a time to see if there was some cel it didn't like; same result.

Any idea why certain LSL5 views aren't working? Someone besides me would like to use this feature if there is a fix for the LSL5 views.

[lskovlun]

In a pinch, you could always use Sierra's native tools, if you can figure them out. They can convert both ways.

[doomlazer]

Do you have a link to the tools?

[lskovlun]

This old thread:

https://sciprogramming.com/community/index.php?topic=1631.0