FGD Errors
#1 posted by
Text_Fish on 2021/11/19 16:05:37
I'm using J.A.C.K (apparently even that's oldskool now!) to make an AD map but the FGD keeps spitting out errors and crashes when I try to open up the properties for certain entities (func_wall for example).
Here are some of the errors when it loads (the complete list won't fit here, but they all follow the same trend!):
Entering: "C:/QuakeDev/ad/ad_1_8.fgd"
Error: parse error at line 540: unexpected token `model'
Warning: undefined base class `PlayerClass'
Warning: undefined base class `PlayerClass'
Warning: undefined base class `PlayerClass'
Warning: undefined base class `PlayerClass'
Warning: undefined base class `PlayerClass'
Error: parse error at line 636: unexpected token `model'
Error: parse error at line 667: unexpected token `model'
Error: parse error at line 679: unexpected token `model'
Error: parse error at line 709: unexpected token `model'
Error: parse error at line 741: unexpected token `model'
Error: parse error at line 772: unexpected token `model'
Error: parse error at line 791: unexpected token `model'
Error: parse error at line 822: unexpected token `model'
Error: parse error at line 829: unexpected token `model'
Error: parse error at line 836: unexpected token `model'
Error: parse error at line 844: unexpected token `model'
Error: parse error at line 848: unexpected token `model'
Error: parse error at line 852: unexpected token `model'
Error: parse error at line 871: unexpected token `model'
Error: parse error at line 906: unexpected token `model'
Error: parse error at line 922: unexpected token `model'
Error: parse error at line 942: unexpected token `model'
Error: parse error at line 966: unexpected token `model'
Error: parse error at line 980: unexpected token `model'
Error: parse error at line 988: unexpected token `model'
Error: parse error at line 994: unexpected token `model'
Error: parse error at line 998: unexpected token `model'
Error: parse error at line 1002: unexpected token `model'
Error: parse error at line 1006: unexpected token `model'
Error: parse error at line 1010: unexpected token `model'
Error: parse error at line 1014: unexpected token `model'
Error: parse error at line 1035: unexpected token `model'
Error: parse error at line 1058: unexpected token `model'
Error: parse error at line 1105: unexpected token `model'
Error: parse error at line 1106: unexpected token `model'
Error: parse error at line 1107: unexpected token `model'
Error: parse error at line 1108: unexpected token `model'
Error: parse error at line 1109: unexpected token `model'
Error: parse error at line 1110: unexpected token `model'
Error: parse error at line 1112: unexpected token `model'
Error: parse error at line 1113: unexpected token `model'
Error: parse error at line 1114: unexpected token `model'
Error: parse error at line 1115: unexpected token `model'
Error: parse error at line 1116: unexpected token `model'
Error: parse error at line 2814: unexpected token `model'
Error: parse error at line 2870: unexpected token `model'
Error: parse error at line 2926: unexpected token `model'
Error: parse error at line 2953: unexpected token `model'
Error: parse error at line 2959: unexpected token `model'
Error: parse error at line 2999: unexpected token `model'
Error: parse error at line 3014: unexpected token `model'
Error: parse error at line 3045: unexpected token `model'
Error: parse error at line 3046: unexpected token `model'
Error: parse error at line 3048: unexpected token `model'
Error: parse error at line 3049: unexpected token `model'
Error: parse error at line 3050: unexpected token `model'
Error: parse error at line 3051: unexpected token `model'
Error: parse error at line 3052: unexpected token `model'
Error: parse error at line 3053: unexpected token `model'
Error: parse error at line 3054: unexpected token `model'
Error: parse error at line 3055: unexpected token `model'
Error: parse error at line 3056: unexpected token `model'
Error: parse error at line 3057: unexpected token `model'
Error: parse error at line 3058: unexpected token `model'
Apologies for the wall of text.
Does anybody know if this is a J.A.C.K problem or a problem with the FGD/AD? I tried to get an older version of the FGD but it seems AD 1.80 is the first to include one.
Wait
#2 posted by
Text_Fish on 2021/11/19 16:38:15
My bad I just opened it up and saw it says Trenchbroom only so there's my answer.
As you were.
BIG NEWS
#3 posted by
Text_Fish on 2021/11/20 16:22:02
I went back further through the archive and found a FGD from an older build that does support J.A.C.K.
Obviously it doesn't allow you to use all the fancy bells and whistles from newer AD's out of the box, but it's preferable to trawling through that horrendous textfile documentation in search of new floats/strings/etc.
Just thought I'd share incase anyone else is slumming it outside of Trenchbroom.
Good Find For JACK Users
#4 posted by
ionous on 2021/11/20 17:26:47
Though I’d urge careful testing with the current AD version to assure there’s no continuity issues.
Yes
#5 posted by
Text_Fish on 2021/11/20 19:54:38
Sound advice Ionous, thanks.
Two Weeks Left
#6 posted by
ionous on 2021/11/23 18:31:56
If you haven’t started, it’s not too late to participate. Still plenty of time to churn out something small.
I'm Hoping To Have Something Finished In Time
#7 posted by
Text_Fish on 2021/11/24 10:18:31
but I keep running in to annoying little issues that I wouldn't if everything Quake weren't about Trenchbroom and AD these days.
Latest annoyance: AD is very confused about keys. My Silver Key door displays the Gold Key door message, but opens with a Silver key. This doesn't happen when I run the map in Copper. I'm guessing it's something to do with AD's additional keys system so I'm sure I'll be able to figure it out, it's just an extra hurdle I could do without for a mechanic that has always just worked straight out of the box for the last 25 years of Quake mapping.
#8 posted by
Rick on 2021/11/24 16:37:07
You should be able to just make a plain "Vanilla" Quake map and run it under AD. I've tested a couple of maps this way and not seen any serious problems. Certain things about AD are annoying though.
#9 posted by
Text_Fish on 2021/11/24 19:21:26
I thought the same Rick, but the vanilla key setup is definitely borked. It was fixed easily enough by adding a message2 string which overrides the default message, but I assume this means that all vanilla maps will display the wrong message for silver key doors, otherwise there's something seriously weird going on with my specific setup!
There's No Such Thing As Stupid Questions
#10 posted by
Text_Fish on 2021/12/01 21:23:06
until I start asking.
So, the AD documentation describes misc_smoke as a "unique model with multiple skins, alpha and ON/OFF states", but doesn't seem to contain any information about how to switch it on and off. I've tried simply targeting it and also a killtarget, but it's not turning off. What am I missing?
Thanks!
Text_Fish
#11 posted by
bal on 2021/12/01 22:10:09
Tried using the entity state system instead? Most AD stuff is made to work with that.
Ah
#12 posted by
Text_Fish on 2021/12/01 23:20:06
Thanks Bal I'll give it a go!
Thanks To All Who Participated
#13 posted by
ionous on 2021/12/07 14:31:59
We had 25 entries total, which is pretty cool. We’re going to doing testing and getting the start map squared away. Ideally we’ll be done in a week; time shall tell.