 News | Forum | People | FAQ | Links | Search | Register |
Log in |
|
|
Short for "Inter-Quake Model". It is (or was?) intended as a replacement for MD5 and SMD skeletal animation formats. It was used in Cube 2: Sauerbraten.
If you want to read a bit more about it: http://sauerbraten.org/iqm/ Anyway, I don't think it's a relevant feature for the average Quake player, rather a feature to cover all bases. Starting from version 0.94.1 and higher the QSS engine constantly crashes when switching between replacing models with MD5 from Quake Release and standard MDL models of Quake ID1 and then loading another map or restarting. Moreover it was tested with upgraded folders (particles/progs/textures, etc.) and with a standard ID1 folder and without MD5 models. All the same, versions 0.94.1-0.94.2 100% crashes when switching and loading another map or restart. On QSS version 0.94.0, everything works fine. Who solved this problem and how?
QS already fixed:
Changes in 0.94.3 Allow loading textures not aligned to 16 pixels and warn about them. QSS 14.10.21: https://quaketastic.com/files/screen_shots/qss_error.jpg I scanned ad-1.8p1, found nothing named 'litebary'. Which map is this?
BTW, the fix in qs-0.94.3 is _not_ meant as a free passport to used non-16-aligned textures: it is an open warning so the modded should fix his thing for compatibility with every other engine. That seems more like a bug in AD, since that is not a valid size for a texture in vanilla quake (therefore most engines)
Just to be clear - the 16-alignment requirement only applies to BSP textures, and the reason for it is for storing all 4 miplevels for use by the software renderer; so: 16, 8, 4, 1 are the minimum allowed dimensions for each miplevel.
The requirement doesn't apply to other texture types. That seems more like a bug in AD, since that is not a valid size for a texture in vanilla quake (therefore most engines)
Indeed it is a bug (just like the bad sky textures sizes in ad_tears), but, as I said, what I can't find is the specific texture mentioned in #292 in ad1.8, i.e. this particular issue doesn't actually seem to be in pristine ad1.8 release. for my wip map. Of course I have already changed the texture size to 64x16 and error gone. But there is few custom wads with such "nonstandard" textures and now in Quake enhanced too. Ericw tools compiled map with this texture as usual.
for my wip map. Of course I have already changed the texture size to 64x16 and error gone. But there is few custom wads with such "nonstandard" textures and now in Quake enhanced too. Ericw tools compiled map with this texture as usual.
The big fat warning is there so that they fix their thing. Same error appearing while trying to run horde2 map from 2-nd updated mg1 episode. Their dev said that it was an unintentional mistake. But it still is a mistake, which we worked around and warn in qs and vkquake. I apologize for unwittingly raising a tempest in the glass, forcing you to look for an error that I generated myself. I want to thank you for your constant willingness to correct the mistakes arising from such idiots as me, nevertheless it is not so easy this is your personal time the most precious thing we have. Thanks to people like you, enthusiasts who spend their personal time, this sailing ship named Quake still keeps afloat, and not only keeps, flies in full sail thanks to the efforts of many. Quake Enhanced was released thanks to the efforts of enthusiasts, former enthusiasts and for the same enthusiasts, united by a common idea. Thank you for your hard work!
has issues with proper entities spawning.
Spoike, please bring back to Your site release 14.10.21 wich has no any issues. Thank You. I put the version on my Google Drive account some time ago. Have fun with it.
https://drive.google.com/drive/folders/19CjLzhEZPjFqERY3rQNXzCz8-qzvSd1h?usp=sharing And then it broke again or it's a different issue? I know some builds had enemies or items appearing in weird places or not at all. Right now I am using Ironwail, anyway.
I noticed that the latest build now has sv_gameplayfix_setmodelrealbox set to 0 by default. AFAIK this is more like original Winquake behavior but differs from longstanding Quakespasm behavior.
For you guys that are seeing issues, do the issues go away with sv_gameplayfix_setmodelrealbox set to 1 instead? If so, it would be good to list some specific examples. I'm not sure why Spike wants to change this default but if it's a real problem, maybe evidence could be compiled toward changing it back.
spike, do you plan on porting antilag code to QSS?
https://github.com/svn2github/fteqw/blob/6871fd24f2a247310a8c31912f300816a4ef1035/specs/antilag.txt Can someone please add the FTE / QSS discord link to the top post for those who want to use it? There is a QSS dedicated channel there: https://discord.gg/E6fTcgB3ev
|
|
| You must be logged in to post in this thread. |
|
| Website copyright © 2002-2024 John Fitzgibbons. All posts are copyright their respective authors. |