So I'm working on some stuff again and digging the new build, however whenever I try to manually set xwin and ywin during the startup script of a map, verge crashes.

It's really just a simple:


void MapInit()
{
cameratracking = 0;
xwin = 1387;
ywin = 246;
}



If I use a function that manipulates those to variables in the start up script, say, one of Kildorf's camscroll functions, that function will work, and it'll end up where I want it to go.

But I'd like it to start at a certain spot on the map to fade in to before I scroll somewhere else.

I also tried it in the last build because I'm sure that's how I used to do it, and it works fine.

Any ideas? :)

Very bizarre! I tested that out on my machine and it worked without problems. I also tried setting xwin/ywin to pixel positions outside of the map to see if that was it, but it made no difference.

What sort of crash is it giving you? Is it outright "windows needs to close this program" or is there an error dialog? If the latter, try copy-pasting your v3.log's text. Might be able to scrape some info out of there.

I may need to see more of the code that goes with this as well, in case there are some other side-effects happening. As a last-resort if you don't want to post here, I can take a look by email (in profile) and I can try to reproduce this error on my machine. Anyways, hopefully we can sort something out.

I actually figured out what was doing it....

I was HookRetracing a simple function that just printed the values of xwin and ywin to the screen. It helps me figure out what to set them at when I want to control the camera. I really didn't think it was causing the problem, as it too would still work fine and appear if I was calling one of those Kildorf functions I mentioned earlier and it's just a call to two PrintStrings.

So that's why I didn't include it in my example code, but, that was my mistake as it's clearly what caused the problem. Commented it out, and voila it works.

I thought I had found a bug, but it was really my noobness.

So, problem solved, but I really appreciate you looking into it for me. :)

Ah alright. Yeah, HookRetrace can get flaky sometimes. I don't mind helping, since it gives me something to do lately.

So what are you working on nowadays? :D

Oddly enough, about two weeks before you made the latest two news posts I felt an urge to get back to work on Amethyst.

So I've been plugging away at it. It's going pretty well, but I don't have anything in a releasable state at the moment. I don't want to make a guess either as my life is pretty busy these days...

But hopefully I'll have something soonish. :)