| |
Instability with V2.6? Displaying 1-9 of 9 total.
1
rpgking
|
Why do people keep saying V2.6 is so unstable? I've been running my game on it, and it hasn't crashed on me once(unless it was a coding error I made). I have Windows ME, and I am running my game in 8-bit, low-res. So does this have anything to do with how stable it is? And I'm not joking about it not crashing on me. It's been as stable as V2k+j, except for the fact that it can handle music a lot better.
-rpgking
Out of clutter, find simplicity.
-Einstein
Posted on 2001-07-07 18:24:53
|
Rayner
|
I agree with you. V26 is stable on my comp (which is running Windows ME). Some people are genuinely experiencing problems and some people are just exagerating it to make tSB feel that he's dumped them with an instable VC version of VERGE that won't be updated. V26 does have it's stability problems but so does every other engine. To the complainers' credit I will admit that when V26 does crash, either do to code error or a bug in the engine itself, it crashes HARD. Not like CTRL+ALT+DEL hard - I mean restart your computer hard :P.
Posted on 2001-07-07 19:09:36
|
TheGerf
|
I've used it a fair bit, and it only screws up when it can't handle resolution or window/fullscreen differences. I'm running win98.
TheGerf, not just any gerf.
Posted on 2001-07-07 19:30:22
|
FlameRainCaptain
|
This only works on Windows 98 or ME. If you have the power button that suspends your computer, instead of power off, you can use the following procedure:
Make sure you have a program you can ALT - TAB to before running VERGE. (e.g. note pad)
When VERGE 2.6 crashes:
Suspend your computer using the button.
Once it is fully suspended, hit ALT - TAB madly. (not a joke)
This should eject you from VERGE.
You can then use CTRL - ALT - DELETE to close VERGE.
This procedure is time consuming and sometimes need to be repeated, but if you comp takes 10 minutes for ScanDisk, it may actually save time.
Posted on 2001-07-07 20:30:16
|
andy
|
I think it's something to do with my DirectX code. It worked quite well on my old voodoo3, I could even run it in 16bpp with the desktop at 32bpp. (the card converted bit depths in hardware)
But when I switched to my GF2MX, v2.6 turned horribly unstable. I can't even run zaril's latest demo (mastercain.com/thequesting if you didn't know) under v2.6 without having to perform a hard reset.
I'll try wining it in Linux sometime. :)
If anyone cares to, reply to this thread with your hardware config, and any comments as to how stable v2.6 is. Maybe a pattern will show up. :)
"I can't wait for this latest pile of melodrama to disappear, so that the VERGE community can once again concentrate on games rather than on itself." -- Joe Lee
Posted on 2001-07-07 21:54:46
|
Hatchet
|
I've never had a problem with it either - I think people complain about it for the sake of complaining. Personally, I think V2.6 is awesome, because it provides an alternative to V2k+j with the same functionality - if the dos version doesn't work, try the windows version, and vice-versa.
-Hatchet
-Hatchet
Posted on 2001-07-08 00:12:24
|
andy
|
It's no more stable under linux. :D
(it is, however, a lot easier to kill off when it crashes)
"I can't wait for this latest pile of melodrama to disappear, so that the VERGE community can once again concentrate on games rather than on itself." -- Joe Lee
Posted on 2001-07-08 01:51:27
|
invicticide
|
... but with MapEd. V2.6 runs perfectly, wonderful, happy :)
But MapEd has a tendency to freak out over stupid little things quite frequently, and it's the only thing making it a pain for me to put together a demo.
For instance, I run MapEd in 320x240 because the proportions look better (320x200 looks like stretchy DOS crap.) Every time I save, the clipping box for the mouse cursor is reset to 320x200, so I can't access the bottom part of the screen. Coincidentally, this part is exactly the same size as the toolbar in the VSP editor. Hmm....
I can correct this problem by pulling up Options... and resetting the resolution back to 320x200, then back again to 320x240. This normally works, but on occasion MapEd will crash with an illegal operation, illegal page fault, or just hard lock. Lately, it's been popping up a blue screen of death (sorta) that informs me that MapEd can't be run in a window... well, duh, that's why I've got it *set* to run full-screen. But that, apparently, doesn't matter.
Also, it's filled with assorted random crashes and hard locks that are really irritating.
I wish, *really* wish someone would pick up the MapEd source code and fix those bugs! (And add hi-res support... would that be too hard?)
That would be cool.
That is all.
--Invicticide
Posted on 2001-07-08 10:39:19
|
rpgking
|
I have an NVidia TNT2(128 bit) graphics card. And my desktop is at 16bpp(I could set it to 32, but I didn't).
Out of clutter, find simplicity.
-Einstein
Posted on 2001-07-08 13:29:53
|
Displaying 1-9 of 9 total.
1
|
|
