v2.6 (vwin) first impressions
Displaying 1-7 of 7 total.
1
Please enter a numerical value for the importance of this sticky.
Enter 0 to unsticky.
grenideer

Well, anyone who has talked to me knows I *hate* v2k. Don't get me wrong - the advantages are great. But the resurgence of old bugs and the persistence of new ones turned me off immediately. Sounds played at half speed, read/write vars never worked, and the engine didn't seem as stable. So let me be the first to thank/congratulate speed bump on v2.6, because I think verge is finally heading to where it should be. Of course it needs a bit more tweaking but it's almost there. These are some points I wanted to bring up:

Read/Write Vars- not sure if it works exactly yet but at least it doesn't crash the program!

music_volume- trying to set this variable kept crashing verge, maybe because there was no music playing? Either way, the log just ended with no explanation.

crashing message- where did these go? with all the crashing and no explantion why, it makes things kind of hard to troubleshoot.

line reading bug- i know that this has to be the easiest bug to fix! Why do we need to start text/dat files with a blank line at the beginning just to get the pointer right? It is ridiculous that this bug lasted throughout all the versions of v2k.

speed- this plays *fast*. My textboxes scale in and out when people talk and in v2.6 I can't even see them scale at all! Everything seems to be moving way too fast and I was wondering if the timing was perfected yet. I hope it can work the same speed no matter what machine you have.

render flashing- whenever there is a render or change to the screen the entire screen seems to flash. this is in 256 color mode too. Not sure exactly what causes this yet.

serious crashing- quite a few times when v2.6 crashes i need to hard reset my computer, one time a soft reset worked. Is there a way for windows to not be as affected by the engine or not? I have win98.

key unpresses- probably has something to do with the super fast speed of the timer, but i can hit enter and 20 textboxes will fly by at one key press. If a char moves or something otherwise pauses the engine, then the key will unpress normally. Maybe I need to stick a tiny wait() at the end of my textbox function, but I don't think I should need to.

I don't quite have all the crashing hammered out yet, and still have yet to successfully save/load, but I'm very optimistic about this engine. Thanks for all the work put into it.



Posted on 2000-12-10 06:16:39

andy

hmm... read/writevars worked fine the last time I checked it. I dunnae.

The thing is, Win9x is a lot pickier about what memory you can and can't use, and when you do something you aren't allowed to do, apparently, it just shuts the app down. There isn't a lot I can do about it right now.

I had the fseekline bug fixed! But somewhere along the line, the source trees got all mixed up, and it's back. :(

One thing that helps tremendously, as far as stability is concerned, is putting the line "safemode" in user.cfg. Also, you should remove any "sound_device" references that are in it. This problem should improve immensely when I can get MikMod up and running. (yeah, yeah, DOS MikMod sucks, but the Windows version is uberswank)

I'm not entirely sure why unpress is being like that. I'll play with it a bit later.

I think the fact that v2.6 cooperates with win98 has something to do with the speed. Windows just takes CPU time from DOS apps when it wants some, v2.6 on the other hand, shares any "left-over" CPU. (I am in control! ph33r!) A delay function would be a necessity for keeping processor speed independance.

That "flash" has to do with the way the engine handles mapswitches. Somewhere in all the loops that map() causes the engine to bomb out, it render/showpages one more time. I don't like it either. As a temp hack, you could use setrstring to null before calling map.

Anyhow, thanks for the bug report!




'What you get by achieving your goals is not as important as what you become by achieving your goals.' -Zig Ziglar

Posted on 2000-12-10 12:59:05

grenideer

Thanks man; it's cool to see you're already on top of most of the problems. As far as Read/WriteVars, in the log it saves/loads fine, but I can't get into my save/load menu without crashing so I don't know yet if the info being saved/loaded is useful or not. But it appears fine.

I was under the impression that the safemode thing was only for sound, and to be used if you were having trouble with sound. Is sound_device not to be used in windows at all, or only if I use safe_mode. Is this the only change to user.cfg?

I know it sounds like I'm making a mistake, but if I set music_volume=20; in my autoexec() without playing music first, the proggy crashes. It will run fine if I either playmusic() first or comment out the set to music_volume.

Keep up the good work man. It looks like Diver Down will be in windows with hicolor after all!



Posted on 2000-12-10 13:41:16

andy

aha! I can fix the volume thing, then! Thanks!

Well, MIDAS in DirectSound is cranky about you alt-tabbing in and out of v2.6, and it bitches by crashing your computer. Fun, huh? Putting "safemode" in user.cfg causes MIDAS to not use DSound. While sound effects tend to play with a bit of latency, it's much safer to alt-tab in and out.

The sound_device thing is my fault, actually. It does nothing now, except that I forgot to make it discard a token, so it parses the next token (usually "0") as a user.cfg command. It then discovers that there is no user.cfg command called "0", so it assumes the end of the file. oops! I fix!

user.cfg is pretty much the same, except you should remove "sound_device" and "dmabufsize" from it. Also, if you're running in hicolour mode, (and have a beefy enough graphics card) you can put "window" in user.cfg to run it windowed! I can run it in any 16/24/32 bpp mode, but some people may need to switch their desktop to a hicolour display mode.



'What you get by achieving your goals is not as important as what you become by achieving your goals.' -Zig Ziglar

Posted on 2000-12-10 14:29:19

el_desconocido

Aside from sound_mode, and rewriting my delay, v2.6 has been nothing but gravy, to me.

I think fseekline() works, but now (properly imho) considers the first line to be line 0.

and even my non-beefy (not even tofu-y: 1 meg) vid card let's me run in a window (with glorious sound), even while online with IE5, Outlook Express, and PSP5 running. (screen shot: http://acmefiles.com/images/v26screen.gif)

And I never imagined how much music would effect the overall presentation...

And I think many of your crashes may be caused by long running functions without updatecontrols() in them. I had a few minor issues with jerky animations and the like, but with updatecontrols() in any function that runs for more than a tick or two, it runs smoother than any previous version. I'm actually able to time our intro to the music being played to within a few ticks.

Oh, and I believe we still need dos4gw at least for vcc and maped.

Hope you stomp all those bugs, v2.6 is better than cheesecake!




-Pontifex
"How many rocks are there, in the whole world?"

Posted on 2000-12-10 18:52:25

TheGerf

The only problems I see is some timing, music/sfx and it doesn't compile half the code, even if it compiles under v2.5. Other than that, it rules.



TheGerf, not just any gerf.

Posted on 2000-12-10 21:18:35

FireMoth

...its made to compile v2k+j. Sorry, but IMHO thats better [mostly of course because my game compiles under v2k+j, and work with slight modifications for v2.6]

-FireMoth



You say America is the home of the free. No man is free if he restricts others. You say America is the home of the brave. When was the last war we fought considered bravery? You say everything is free in America yet you let companies over-advertise till t

Posted on 2000-12-11 17:06:23


Displaying 1-7 of 7 total.
1
 
Newest messages

Ben McGraw's lovingly crafted this website from scratch for years.
It's a lot prettier this go around because of Jon Wofford.
Verge-rpg.com is a member of the lunarnet irc network, and would like to take this opportunity to remind you that regardless how babies taste, it is wrong to eat them.