It's -Fno-fastarrays for reference.
#pragma flag disable fastarrays
Uploaded a minor update to the fgd file for better compatibility with GTKRadient. The fgd parser for GTK is a little stricter than the worldcraft one - the two crucial differences I've discovered are:
* PointClass, SolidClass and BaseClass are case-sensitive and must be written in CamelCase to work.
* It is not permitted to omit the description string which follows the classname for a PointClass or SolidClass entity. In worldcraft this is an optional entry.
So the new version of the fgd complies with these two rules. Does no harm but makes no difference for Hammer/Worldcraft users, lets you load it in GTKRadient. Note it appears you must jump through some hoops to get it working in GTK - I had to rename it halflife.fgd and place it in a folder called "valve". Plus a few of the .game file settings have to be copied exactly from the half-life .game file to get things to work.
I'm sure there was a way to convert fgd into a def or ent file, but can't seem to find it anywhere online...
were not part of the fgd with trenchbroom, are they in this one?
...but they would be very easy to add. On the other hand you hardly gain anything over just manually typing in func_detail, because it's an entity with no key values, just a classname.
Found A Problem
I get this message when opening WC3.3 using the latest Quoth2.2 .fgd
error parsing c:\.....\quoth2.fgd line 1166 expecting '=' but found '.'
error parsing c:\.....\quoth2.fgd line 1310 expecting identifier
Is it important or can i ignore it?
Looks like there are some places where 3.4 is less fussy than 3.3. Both look easy to fix though, so I've uploaded a tweaked version. Give it a try and let me know if it sorts things!
Seems To Work
no messages this time.
Thanks for the instantaneous fix.
Just noticed this: load kellbase1.bsp, and noclip to the orange room with the water pool, just behind the info_player_start. Kill one of the pyro enforcers.
DP spams the console with: "WriteDest: Tried to write to non-client"
Fitz 0.85 and QS freeze for a second and then drop you at the console with this:
WriteDest: not a client
Host_Error: Program error
Client ericw removed
This is on quoth 2.2.
Hi ericw. The log from the console tells me that the pyro is killed, the trigger_counter bumps the numbers, tries to broadcast the message to all players, picks an entity to broadcast to, and then crashes. The error is that the entity picked was not a player, and sending the message to a non-player is a no-no in Quake. However, there is already code which is meant to limit the messages to players, and I can't replicate the crash here with any of those engines.
If it's consistently replicable at your end, can you make a save game before you crash the game, and e-mail me that save game and your config.cfg/autoexec.cfg files, so I can see about fixing it.
It turns out I was downloading quoth2pt2full.zip which had an older (2014) pak2.pak than quoth2pt2patch.zip (2015).
Preach updated both the full and patch zips (thanks!), so you may want to download the patch if your pak2.pak is modified in 2014.
Ooh, I didn't know that. I have the full version so I'd better check it out.
No wonder I had so much trouble with the last jam.
Umm, you mean map jam 7, I suppose? The last one runs in AD.
Someone just told me that doing -game warpspasm -quoth doesn't play the startdemos.
I know this wasn't on purpose.
I wonder if there are any other standalone-like releases like The Living End or such that are also impacted.
I'm just raising awareness of the change of behavior.
/I will probably have Mark V block loading of Quoth 2.2 pak2.pak (just have it load up pak0 and pak1) for Warpspasm eventually, since you implemented a very organized structure for falling back to the previous version.
The full zip on Preach's blog still has the pak2 file from 2014?!
Not for me, I just dl'ed it again and the pak2.pak is modified nov 2016. The link on https://tomeofpreach.wordpress.com/quoth/
Maybe some kind of caching issue?
Maybe is time for Quoth 2.3 since Quoth 2.2 can have so many different meanings.
The March 2015 and Nov 2016 pak2.pak's are identical (just checked with 'diff').. so I guess March 2015 is the actual last modification date.
I re-installed Quoth 2.2 last week, my pak2.pak is same as negke's (May 3 2014) from Quaddicted.
And if you look at this page, and the file dates for the pak files ...
There have been in effect two "point releases" of Quoth since 2014, each of which fixed one bug that occurred rarely but was troubling. They really should have been called 2.2.1 and 2.2.2 but it's too late now. Quaddicted has the original zip (2.2.0), the version on my site has the updated one (2.2.2). I think Quaddicted is the only major mirror of the mod, so if that can be updated then it should all be fine.
When I go to download this file ...
Which ericw says has pak2.pak dated November 2016, like negke the contents say May 2014 for me.
So I open entirely different web browser than normal to make sure and download. Same problem. May 3, 2014 :(
Dumb question: As I understand it, Quaketastic doesn't let you delete or replace ... so can't be an internet caching issue (like what CloudFlare does) because same file couldn't have upload twice with same name?
Replacement On Quaketastic
As I understand it, Quaketastic doesn't let you delete or replace
It does, and that's what I did. Maybe your ISP has some kind of caching layer which is messing this up?
which has a different filename so should circumvent those issues.