#322 posted by trinca on 2010/02/24 20:38:55
finaly got home and try!
FUCKING YEEEEEEEEEEEEEEEEEE
is working
/me kisses Mr Fribbles
Yeah...
#323 posted by metlslime on 2010/02/24 23:21:50
I removed ztrick long ago. It was basically a hack to avoid clearing the z-buffer between frames, at the cost of half the z-buffer precision. It didn't play well with my sky rendering code, plus it's not needed any any card newer than the voodoo1.
MP3 In Fitz0.85
I'm using the fitzquake085_mp3 build supplied in Baker's mp3 support tutorial but I can't get it to actually play any mp3 files. :(
I have no idea what could be possibly wrong. My soundtrack is in id1\music (or travail\music for that matter), and not within a .pak either. The playback related console messages appear for me, and I can use the mp3 commands just fine (without any errors that is). Nothing plays, still.
Is it as simple as turning it on with a cvar, or something?
Travail Music
#325 posted by Baker on 2010/03/06 17:14:27
You have to use these mp3s due to the file names:
http://www.quake-1.com/files/modfiles/travail_soundtrack_mp3_easy.zip
They go in id1\music or travail\music folder.
Um
I have already renamed the mp3's myself beforehand. I also have the original Quake soundtrack in id1\music, also named track##.mp3.
On Start Map
#327 posted by Baker on 2010/03/06 18:25:15
If it says ...
"track name is 03"
"playing track03.mp3"
Then check the volume control in Windows.
If it is just saying ...
"track name is 03"
and doesn't say "playing track03.mp3"
Then you don't have track03.mp3
If you aren't using -nocdaudio and aren't getting either of the above messages, something else is wrong.
It says:
Track name is 03
playing track03.mp3
It's not my sound being disabled from within Windows, either, I can listen to anything else just fine.
Stupid Test
#329 posted by ijed on 2010/03/06 18:56:37
Have you tried renaming any old map and replacing one?
After testing several maps from several gamedirs, I can safely say it's not a mapside problem ;)
..
#331 posted by Baker on 2010/03/06 19:12:37
If it says playing, you can rule out everything the user is doing as a problem. It isn't the map or anything else.
It's either the engine, DirectX drivers or possibly Windows settings somehow.
In the future, I'll get broader testing of the change to get wider feedback. This modification hasn't had broad testing at this point.
Dear Fitzquake
#332 posted by gb on 2010/03/07 01:24:18
These are some features I think any Quake engine should have these days:
1. connect blah:port working well (this is the game that introduced online multiplayer after all)
2. NAT fix
3. Ping in scoreboard (it's just useful)
4. Support for fake CD tracks from ogg or mp3 files
The reason for having the basic multiplayer functions is that some people test their multiplayer-capable mods in Fitzquake because they're doing singleplayer maps as well.
The reason for the ogg/mp3 support (ogg is fine) is that finding and swapping and maintaining and storing CDs is a nightmare, especially since Quake CDs are getting older and rarer, and the Steam version doesn't come with the CD.
Ug
#333 posted by ijed on 2010/03/07 02:16:03
My stupid test suggestion was made stupider. I meant to say 'mp3' not 'map'.
Also
#334 posted by ijed on 2010/03/07 02:22:54
An SP engine feature request / question.
Could we have global sounds play genuinely globally, and not only when in the player's LOS?
#335 posted by gb on 2010/03/07 04:46:55
Yeah, that should go into QSB 1.0.
Sorry for thread hijacking :-P
Condebug Lag
#336 posted by negke on 2010/03/09 13:12:31
Unlike other ports, Fitzquake freezes for a couple of seconds when using the edicts command in conjunction with -condebug.
Interesting... I'll Have To Check That Out.
#337 posted by metlslime on 2010/03/09 23:27:25
Edicts Command With -condebug
#338 posted by mh on 2010/03/20 02:07:05
That actually sounds normal enough. The edicts command spews a *lot* of text to the console, all of which is written to the HD using unbuffered IO when -condebug is enabled. I'd be surprised if an engine does anything other than freeze for a short while, in fact.
Yeah...
#339 posted by metlslime on 2010/03/20 05:06:06
the solution is to buffer that stuff, but the negative of buffering is if you crash before you flush the buffer, you end up not logging whatever was buffered.
I guess it depends on what the primary use case of -condebug is. If it's diagnosing a crash, vs. just a convenient reference for later use.
#340 posted by negke on 2010/03/20 10:25:16
Well, it works flawlessly in GLquake and Ezquake for example. Winquake freezes, too.
The delay varies depending on the OS. On XP, it takes roughly 40 seconds for E1M1, on Win7 almost 100 seconds (and I even had to close it from the task manager afterwards). GL seems to handle the buffering differently then?
Necros:
#341 posted by metlslime on 2010/03/20 21:26:37
ah, good to know. I can look at how they do it, maybe i did break something.
#342 posted by mh on 2010/03/22 19:38:57
> Well, it works flawlessly in GLquake and Ezquake for example. Winquake freezes, too.
That's odd because it's the same code in WinQuake as in GLQuake...
On my linux C2D box, there's a noticeable delay, but nothing really. Day of the lords with 144/166 kills takes less than 2 secs with -condebug. Whatever it is, i think it's in quore-0.3.0 too, which uses some fitzquake code.
#344 posted by Spirit on 2010/03/22 21:33:06
1s here (athlon 2 x2 240). Exe: 16:04:11 Jul 5 2008 on Lunix.
One Difference...
#345 posted by metlslime on 2010/03/22 22:05:56
The original glquake generally would redraw the screen once for every line of text printed to console. For large dumps (like the edicts command) this took a long time, so I changed it to write everything first, then update the screen once at the end.
This is faster overall, but results in a small period of no screen redraws. Since in my testing it only takes a fraction of a second, I never saw this as being a problem. I suppose that with -condebug, it takes longer and this hang is noticable. However, the alternative is that printing 500 lines takes 500 render frames, i.e. like 5+ seconds.
I still haven't tested this so it may be there is some other dumb bug causing the lag. But that's my current theory.
#346 posted by necros on 2010/03/22 23:01:07
i guess there's some coding reason why you couldn't just make it print 100 characters at a time instead of all or nothing?
|