I will keep a list of bugs and their status and any workarounds in this thread. Feel free to post below any bugs not listed and I will edit this post to include them.

HookTimer causes crashes on some systems
It seems to work fine on most people's systems (including mine) but crashes on others, which makes it hard to track down. This currently effects Timeless and the PepperII clone.
Status: Fixed in the next EXE.

verge.exe leaks memory and slows down after many successive launches
This is really a Windows problem, as the OS should not allow any process to leak memory. However there are things v3 can do to minimize it, which will be addressed later. Seems to vary from system to system a lot, suggesting it is a driver bug. On my own system, almost every app leaks memory, but at a pretty slow rate.
Status: Probably will never be completely eliminated, but steps will be taken to minimize it. However it is a lower priority item at this point.

AVI Playback problems
Yeah there are some problems that vary wildly from machine to machine. AVI playback is still a feature under development. We strongly recommend not using codecs like XVID/DIVX for the time being, if for no other reason than that not everyone has them installed.
Status: Still under active development.

Fullscreen flicker
On my system, the mouse cursor won't hide in fullscreen mode and the tray icons flicker through on top of the screen, which also results in a significant loss of FPS. zeromus has no such problems. This happens to me in a whole lot of fullscreen games, including 3d games, one of may reasons I much prefer to play in windowed mode. But I know there are games that don't so I know it can be corrected.
Status: Presently being actively researched by zeromus

Windowmode frame flicker
Sporadically, maybe every minute or so, a single frame will be off on some video cards. I have a dual monitor system with two video cards and on my Voodoo this never happens, but it does on my Geforce. This is NOT a blitter issue, its some problem in the directdraw code. Similar to the fullscreen issue, on my system there are a lot of other programs that do this, including some emulators such as GENS.
Status: Actively being researched. Most likely to be fixed with DirectX9 based ddraw code.
Workarounds: Turning down the hardware acceleration option generally fixes it, but its a pretty crappy workaround. The problem is fairly minor, so I suggest you just wait till we fix it.

VCC line number reported on errors are off
Yeah, yeah. Generally speaking if it not on the correct line, it will report the line+1 where the error occured. Usually because its reading the next token before it realizes that it doesnt make sense. It can be more than 1 line off with for loops.
Status: We will work to improve it, but it is a low priority item. It was like this through the entire history of V2, you should be used to it by now!

Some ITs and XMs do not play correctly in FMOD
FMOD plays all IT and XMs correctly that were generated by Impulse Tracker or FastTracker. Modplug Tracker saves both of these formats however sometimes does not adhere to the standard.
Status: An FMOD issue, not in our control
Workarounds: Generally the module can be corrected to work properly in FMOD. If you are not tracker savvy however, you can always convert it to an mp3 and play it that way in FMOD. We also hope that this issue will be directly addressed in the next version of FMOD.

Some modules do not loop in FMOD
Some modules intentionally do this. They are using order jump commands to loop silence at the end rather than actually ending.
Status: Not a bug.
Workarounds: This can only be fixed by editing the module. If you dont know how, jump on #vergehelp, someone can probably do it for you.

// My crash list

int out_of_bounds[2];
int too_many_args(int a) {}
string empty = "";

// THAR BE CRASHES BELOW

struct crash { int me[0][1][2][3][4][5][6][7][8][9]; }

// 951 characters or more will cause a crash
string too_long = "...";

void unbalanced_braces_1() { int"; } void"() {}
void unbalanced_braces_2() { int {; }

void autoexec() {
out_of_bounds[2] = 0; // fixed
CallFunction("too_many_args");
MessageBox('"');
MessageBox(empty);
}

#include crash" // fixed
#include "crash

We havent released a new exe with the fix yet.

I'm not sure if this is a bug, but it seems that it is quite possible to get it stuck where you can only get out by resetting. If you have some code that is looping over and over only performing mathematical calculations, alt-X won't work. Alt-tab also fails to minimize, and the windows key just makes the windows mouse icon appear over Verge without actually letting you out.

See, I'm working on this random terrain generator, which has to iterate through a pair of nested for-loops (512x512), which is itself contained inside a while loop. The for-loops conduct calculations and set elements of a massive array based on the calculations, and the while loop only breaks when certain conditions are met. While working on this, it is very easy to misjudge the math and end up with an infinite loop.

Is there a way to make alt-X work no matter what?

Having a period in your function name will cause a v3 to not compile your code.

example:

void Place.Portrait()


{





}

The above will not work, but it did in V2. What's the deal?

BTW, whenever I run verge 3 and then open a full-screen dos prompt (or any full-screen text mode thing), when I switch back to windows, it crashes (in "oldwinapp" or something I think). I use win98se. This could be a memory leak issue or a video driver issue rater then a bug in verge 3 though.

Technetium: Yeah, it's kind of odd, because in effect, PlaySound is no different than PlayMusic because of the looping. There should be a argument to specify whether the sound should be looping or not. This CAN be worked around now, but it would require yet another hijak of the render loop or a hooktimer.

1. Regarding random crashes, are you using HookTimer? If so, did Timeless work for you? There is a known bug in HookTimer.. but only on certain systems, and none of the systems are ones that any devs have access to at this time, which presently makes it tough to debug. Interestingly, hookretrace works just fine on these systems.... so its not a VC-reentrancy issue... its something to do with the TIMER. Which concerns me.

2. Two questions, first, are you using the most recently released EXE? Secondly... How big are we talking about? If you would, post the v3.log text, which will say how many ints, strings, structs, functions, and lines were compiled... also, post me the length (in bytes) of your system.vc, as well as the length (in bytes) of system.xvc. That should give me an idea of where the problem lies.

Sorry, I didnt see the sound effects thing earlier.

Uhh.. as far as I know - you're using the FMOD build, right? Sound effects do not automatically loop, we certainly don't do this intentionally. I have tested the SFX in our development on Sully and they seem to work fine.

What I imagine is happening is possibly that if some loop information is embedded in the WAV, then FMOD is obeying it. I'm sure its possible for me to explicitly set it to not-loop, and I'll take a look at that. If you can, send me a WAV that automatically loops on IRC sometime and I'll test it.

As far as the random crashing goes.... I havent experienced this outside of HookTimer, so, I guess, just let me know if you manage to narrow this down or get any more information on it. I personally have left timeless running for about a 16 hour period without crashing so, whatever it is, its not really random, its specific to some thing that you're using that probably no one else is. ^_^

I have tested four different sound effects for the same function. Two of them loop over and over, and two do not. They are all 8-bit, mono-, and non-looping (according to Modplug Tracker, anyways). maybe there is some extraneous information put in the file by the program that made it that is somehow being misread as loop instructions.

I'll look for you on IRC so I can send you one of the ones that doesn't work.

About the crashing... it's not really random. It will only happen when a function is being called from within the autoexec function (mainly when you make a menu choice on the title screen, as two of those choices call other functions). But it happens sometimes and not other times.