Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Error: Unexpected Symbol when converting RtCW def #2

Open
SirYodaJedi opened this issue Jan 16, 2023 · 2 comments
Open

Error: Unexpected Symbol when converting RtCW def #2

SirYodaJedi opened this issue Jan 16, 2023 · 2 comments

Comments

@SirYodaJedi
Copy link

When attempting to convert the def file for Return to Castle Wolfenstein from GtkRadiant (1.6.6), I get the following error:

wolf_entities.def:661:27: error: Unexpected symbol

I am using the v1.2 release of def2fgd as found on the releases page of this repository. When looking at row 661, column 27, that character appears to just be a space, so I'm not sure what the unexpected symbol could be.

@FreeSlave
Copy link
Owner

Hi. It's because the entity alarm_box doesn't define the bound box.
Change

/*QUAKED alarm_box (1 0 1) START_ON

to

/*QUAKED alarm_box (1 0 1) (-8 -8 -8) (8 8 8) START_ON

There will be another problem, at line 1227 though.
Change

*/
/*
"fxdensity" size of explosion 1 - 100 (default is 10)

to

"fxdensity" size of explosion 1 - 100 (default is 10)

Thanks for providing the faulty .def file. I'm not sure when I update the code to handle these cases, but I hope fixes I provided above will help.

FreeSlave added a commit that referenced this issue Jan 17, 2023
@SirYodaJedi
Copy link
Author

Thank you; those changes allowed it to run. Now I just need to clean up some of the conversion mistakes (def is such a messy format compared to fgd, so those are to be expected).

Feel free to rename/close this issue as you see fit. Idk whether your recent edit fixed handling this issue, so I don't want to close it if it's not fixed.

Garux pushed a commit to Garux/def2fgd that referenced this issue Oct 12, 2024
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

No branches or pull requests

2 participants