Linux crashes on #include from Description.ext
Reviewed, NormalPublic

Description

After some trouble today and some help from the community via Discord I've finally given up and decided to report it.

When you use a #include inside a Description.ext it works fine when testing locally MP on Windows, but when on Linux it's crashing the server.

Details

Severity
Block
Resolution
Open
Reproducibility
Always
Operating System
Linux x64
Category
General
Steps To Reproduce
  1. Setup the files on server and client. (https://drive.google.com/open?id=0B2VDMa242aajU0doOExCdlBXZVk)
  2. Startup the server with @test and connect to it.
  3. You should lose connection because server has crashed due to 'Include file test\testfile.hpp not found'. Even though the mod and file is there.

When tested on locally MP it works fine.

Additional Information
Raabit created this task.Thu, Jul 13, 7:13 PM
Raabit edited Steps To Reproduce. (Show Details)Thu, Jul 13, 7:16 PM
dedmen added a subscriber: dedmen.EditedThu, Jul 13, 9:55 PM

#include from external source (Not inside mission folder) inside packed Mission pbo's is known to be broken since Eden. On Windows and Linux.

Also this is not a real crash. It just throws the fatal error "Include file not found" which needlessly kills the game instead of just failing to load the Mission.

Probably related to part of the PBO Header disappearing from Mission PBO's packed by Eden.

@dedmen But it works fine while doing it locally MP, not sure for Dedicated Windows though.

Also something that I've noticed while testing this, it looks like that all missions (Description.ext) are read when going to the host local screen. I got booted out of the game multiple times because I had missions with #include but didn't load the mods for them. Probably made like this if not it will be an other issue for sure.

Yeah that's intended. Because the description.ext can set the display Mission name via briefingName I think it needs to be parsed when the Mission's Name needs to be displayed.
You can also define a Picture to be shown in Mission selection so that's also a reason why it needs to be parsed.

Are you sure you are testing the PBO'ed mission in the MPMissions folder in local MP? Because if you load the unpacked Mission folder from your My Documents thingy then that Indeed works.
As I said only packed PBO's are influenced.

@dedmen Just tried it and yes I crashed when Testing it with the PBO Locally as well. So seems like its a overall issue.

I guess issue could be closed then if this is reported on a different issue.

razazel claimed this task.Mon, Jul 17, 1:00 PM
razazel changed the task status from "New" to "Reviewed".

Add Comment