Yes, this build is WAY late, but here it is. You can view the full changelog, and here's a new v3vergec.txt reference. Hopefully you'll see the online doc section updated to reflect the new hotness soon. Short version is there's several key bugfixes, including big improvements with line number error reporting. New stuff including FlipBlit(), a set of functions to get/set a variable value by its name, some new functions to interact with the windows clipboard, and a number of new variables, including curmap.tileset which provides an image handle to the current map VSP, that you CAN draw to (the image will be 16 pixels wide and 16*numtiles tall).

Planned binary-tree based optimizations did not make it into this build in the interests of just getting it done so you'll believe me when I say we're not dead. I did however add a new verge.cfg option that controls whether or not vcc_verbose.txt is generated during compilation, which defaults to off, and on large projects, this will reduce compile time by a noticable amount. Tree optimizations later on will improve compile time further as well as the lookup time for CallFunction and the new variable Get/Set functions.

We also added a small splash screen that appears when V3 is compiling to let people know that v3 didn't crash on startup or anything when compiling large projects that aren't in releasemode. I just whipped this one up in photoshop in literally thirty seconds. I will happily accept submissions for sexier screens. The general guidelines are that it should be a 320x200 GIF that will be displayed centered in the screen for larger resolutions. If anyone is interested in making a better compile screen, feel free to just post it in the comments for this post.

You may not believe me, and I won't blame you, but I do mean to try to get back on a every-week-or-two release schedule for the engine. So feel free to submit additional feature requests and bug reports here as well. I read the forums as much as I can but stuff does slip through. Grue also tells me you all can expect a new Sully build in a few days, so if he doesn't come through, I encourage you to throw rotten vegetables at him, such as brocoli or cabedge or perhaps carots.

I was wondering if you could get at the ints in structs with GetInt (you can't could you put that in please)
I found it crashes if it can't find the varible with SetString (I didn't test the others)
thank you for the get and set int and string arrays that will be of great help

Quote:Originally posted by Ness

So I put the new exe in my dev directory, start it up in compile mode, and it compiles IN 2 SECONDS. As opposed to around 40 for the old version.

All I can say is .....word.....

VCC Verbose: the silent killer!

Yeah, Sully compiles in mere seconds now too. I had no idea it was a massive log-writing excersize that was slowing everything down.

The best thing about this build IMO tho is the improved error reporting. Yaaay!

Yeah. Likewise, if you run the Sullycode with verbose logging on, you can be waiting for... quite a while.

Wohoh! SetRandSeed is fixed! TIme to go and play moar...

Zip

Quote:Originally posted by vecna

I encourage you to throw rotten vegetables at him, such as brocoli or cabedge or perhaps carots.

omgcabedge *wip*

Heh, it even crashes faster when you do an array out of bounds

Oh and error reporting on the line that actually caused the error is nice to

New Sully to show off the sexification?
eh? EH?

And where the fuck are those diagonal directions, vec?!
EH?!

Could we get an Ascii(string chr)?

Alright, here are my questions about a lot of the changes...

Rendermap(): Can this render areas larger than what would normally fit on the screen? For example, if I made a new image that was 5000 by 5000 pixels, and used rendermap at (0,0), would it render as much of the map as it could fit? Also, does it render from 0,0 on the map, or does it begin dependant on the xwin and ywin variables?

CopyImagetoClipboard: I'm confused on the use of this function. Does it let programs outside of Verge access this clipboard? If not, can't we just get the same effect by creating a new image and duplicating the old one over it?

curmap.rstring: is this read-only, or can we write to it as well?

layer.lucent: I assume this is an array. Is it layer[].lucent or layer.lucent[]?