#514
#516 posted by
mh on 2022/05/18 18:48:43
Ironwail does have a hard-coded MAXALIASFRAMES of 256, and does do a bounds-check on that which causes the Sys_Error; that came into QS in version 0.94.0 as well, according to the change log, and this is the source of the crash-to-desktop and associated message.
I guess that upper-bound needs to be changed in both engines as both 666 and 999 can exceed it. I'll log a bug for Ironwail.
#514
#517 posted by
mh on 2022/05/18 18:52:59
#516
#518 posted by
szo on 2022/05/18 19:03:51
MAXALIASFRAMES check was added to prevent out-of-bounds access to poseverts[MAXALIASFRAMES] array:
https://sourceforge.net/p/quakespasm/bugs/37/
I'm A Fool
#519 posted by
madfox on 2022/05/18 19:17:56
alright. After checking out all updates from quakespasm 0.94.0 to 0.94.4 I blew up my own configuration where it just runned the mod fine.
This was with protocol666.
Some questions.
Is my mod corrupted, or was I to lame to see why all concerns people made with complaints my fault?
How can I change the protocol 15 to 666, or isn't this possible as the code is hard edged?
I feel a bit noob, as I get the feeling I'm a victim of novilty?
Madfox
You can change the protocol with sv_protocol 15 for example in the console. Do a restart after entering it. Thanks to mh Andrei has increased this to 1024 in a commit. So next release this won't be an issue.
Thanks for the clarification @mh and @szo
Screwed
#521 posted by
madfox on 2022/05/25 03:22:49
I can reset my fitzquake0.85 to sv_protocol 666 as much as I want, but after a reset it stays this way one time.
As soon as I try to play the mod it bounces back to 15, reclaring back the error.
Wish I never tried the update.
Madfox:
#522 posted by
metlslime on 2022/05/25 21:23:52
a potential problem is the config.cfg being different between id1 and your mod. Not sure about this, but I think when switching games in quakespasm it reloads the config from the new mod folder, which could set your sv_protocol back to 15 even if id1 has the protocol set to 666. Then when you quit the game, it writes a config file but only to the current mod folder. Try using a text editor and editing config.cfg in both id1 and your mod folder to have the correct sv_protocol
Thanks
#523 posted by
madfox on 2022/05/26 03:59:02
On another computer my quakespasm_0.92 used protocol 666. Until I installed the updates.
I will try with Teath, see what it will do.
It could be done with a config.cfg in the mod itself.
Remaster Planned In October
#525 posted by
CV on 2022/09/21 17:34:18
#526 posted by
madfox on 2022/09/22 14:45:24
I'll return to my old school.
Doesn't Look Too Remastered To Me
More like a re-release. At least I can't see any significant visual improvements.
#528 posted by
Tribal on 2022/09/23 17:05:13
Yep, it's more like what Nightdive did with Quake.
I think they are just fixing compatibility issues between Chasm and Windows like mouse input, resolution, framerate, sound delay, etc..
Results
#529 posted by
madfox on 2023/01/27 15:49:15
Updating the last link.
I managed to transfer most entities to quake except Worm and Chair. Quake has not the same advances Chasm beholds, so I left them for what they are.
http://home.kpn.nl/lo2kf8/quake/maps/Quasm_dev2.46.zip
The posenum=Maxalias seems to be vanished.
Different engines different compatrible.
They Yeeted Your Page MF
#530 posted by
xaGe on 2023/11/06 06:21:20
All you get now is:
"This homepage no longer exists. KPN stopped KPN Homepages on September 20, 2023."
I See
#531 posted by
madfox on 2023/11/12 04:56:25
Turned it over to Quaketastic.
Eaiest way to do it, I think.
Quasm_Quake_dev2.456
#532 posted by
madfox on 2023/11/12 04:58:51
link gives the weong paraph, it is in
single_player/mods/Quasm_Quake_dev2.46.zip