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

[troflip]

Yeah, pretty sure it's fixed. Or at least the problem that gets you into that state is fixed.

[MusicallyInspired]

This is what I've been playing around with since the release.

[troflip]

Hey, that looks great! So those are graphics resources from a fan-made KQ1 done in another engine, right? And you're re-making it in SCI 1.1?

The palette cycling looks pretty slick.

Looks like you'll need some polygons soon

[MusicallyInspired]

Yeah, they're borrowed from AGDI's remake made in AGS. Not as easy as you'd think. Screenshotting animation frames is a paaaaaaain. Won't be finishing this. Just for the experience to work out some of the advanced features in SCI1.1. If I ever did do this I'd want to finish KQ2SCI first. I did the logo image in Deluxe Paint and Grafx 2 (a modern spiritual successor to Deluxe Paint). It was fun to create I liked how it turned out.

[Kawa]

Y'gotta love those button borders.

[Collector]

MI, isn't there any utility that can extract graphics from an AGS game?

[OmerMor]

Or better yet: you've worked with AGDI. Won't they give you access to their graphic resources?

[MusicallyInspired]

MI, isn't there any utility that can extract graphics from an AGS game?

I had thought that Chris Jones specifically designed AGS so that nobody could decompile or rip assets from it.

Or better yet: you've worked with AGDI. Won't they give you access to their graphic resources?

That's a lot of content. With us still working hard to finish up Mage's I doubt they'd have the time. Especially when I'm still finishing up music! Chris Warren (AGD2) liked the logo though lol.

[Kawa]

I had thought that Chris Jones specifically designed AGS so that nobody could decompile or rip assets from it.

You know that's impossible. Difficult maybe, but theoretically it can be done.

[Cloudee1]

Copy and paste from one cel in a loop to another cel in the same loop, causes all kinds of bad things.

In the screen shot, cel 1 was copied to cel 2.

[troflip]

arghh...  (also, you mean loops/views, not cels/loops). Yeah, I broke this when I "fixed" things so that copying among view cels with the same palette just did a direct copy (instead of re-interpreting RGB colors).

Well, you can work around it in the meantime by making the bottom cel the same size of the one you're copying from, then adjusting (and wouldn't you need to do that anyway? If you're trying to make a small version of the plunger, you'd want to copy the old one into a same size cel, and then re-size it by SHIFT-dragging a border).

[Cloudee1]

Yeah, that is just what I was going to add, that it only happens when the second cel is smaller.

When I did it, I didn't think about the cels being different sizes, I was just copy and pasting without a care in the world

and yeah I did mean cels of different loops... I'm not used to the right pane showing loops and the bottom pane showing cels yet. But it also breaks with cels in the same loop if the second one is smaller

[MusicallyInspired]

I've run into this. I saw that it was a size issue and just worked around it. I do like the idea that when a cel is smaller the pasted graphic will be resized. However, sometimes I'm working so fast I might not notice that it's smaller (take walk animations for instance) and I'll end up with skewed animation cels. This isn't a feature request but a request for feedback on a potential feature. Does anyone think it would be too bothersome and time wasting to add a pop up window warning that the image being pasted is larger than the size of the cel it's being pasted in and asking for confirmation before proceeding?

Y'gotta love those button borders.

If you're talking about the ones on the title screen, those are actually Views. lol

[Kawa]

If you're talking about the ones on the title screen, those are actually Views. lol

I know they are. I was joking about the lowlightColor thing.

[MusicallyInspired]

Actually, if you'll notice, the insetWindow for the Inventory GUI still uses grey colours. I have to find that and fix it. My first attempt proved fruitless. It's probably a global variable thing, which makes finding the point at which the colours are set difficult because you don't know what to search for right away.