Jump to content
Sign in to follow this  
Duke101

Description.ext issue/help

Recommended Posts

Hi,

Hoping someone can help.

I'm having a strange description.ext problem.

Just starting a fresh new mission- named it and saved it. Added some 'standard' scripts I use, init.sqf and des.ext, etc. copied straight from the previous mission, which works perfectly.

It appears that the description.ext is not loading at all. I'm getting errors where I have scripts running fine from the init, because they're not loading from the des.ext. The loadmission name isn't showing correctly. I have left it blank, written 'test', etc, etc. and I get on the loadscreen when I preview in the editor is the name of the new mission folder I created ? I even purposefully wrote some gibberish in the description.ext and no crash or anything ?

First time I've come across this, but it is as if the des.ext is not being read. I tested several older missions and have no issues at all. I've created several new missions and I'm getting the same issue with des.ext.

Any ideas/help would be greatly appreciated.

Thanks.

Share this post


Link to post
Share on other sites

Make sure that you have re-saved the mission again (with SAVE or SAVE AS) to ensure that the files are included in the mission folder.

Share this post


Link to post
Share on other sites

Make sure it is not saved as description.ext.txt, that could happen if you have extensions of files hidden while your text editor saving it a .txt by default.

Share this post


Link to post
Share on other sites

Thanks for your replies guys, it's appreciated.

Well this morning I set up, as @CRY3rn suggested, just a very simple mission and the des.ext was working ! I slowly added things to this test mission, with an init, etc and all seems to be working fine.

I did all the fundamentals and rechecked, etc. at the time yesterday (at least I think so).

@CRY3rn I agree with you- my thinking was the same. If my old missions were working fine, then surely the problem couldn't be that fundamental and that turns out to be the case.

It was late for me and I was tired. I can only assume that I missed something or screwed something up without noticing. I honestly don't know what the issue was.

Lesson learnt- don't start messing with a new mission when it's late and your tired.

Thanks again all, it's appreciated and sorry to have wasted your time.

---------- Post added at 09:48 ---------- Previous post was at 09:46 ----------

Thanks for your replies guys, it's appreciated.

Well this morning I set up, as @CRY3rn suggested, just a very simple mission and the des.ext was working ! I slowly added things to this test mission, with an init, etc and all seems to be working fine.

I did all the fundamentals and rechecked, etc. at the time yesterday (at least I think so).

@CRY3rn I agree with you- my thinking was the same. If my old missions were working fine, then surely the problem couldn't be that fundamental and that turns out to be the case.

It was late for me and I was tired. I can only assume that I missed something or screwed something up without noticing. I honestly don't know what the issue was.

Lesson learnt- don't start messing with a new mission when it's late and your tired.

Thanks again all, it's appreciated and sorry to have wasted your time.

Just in case you're curious...I found out what the problem was.

I didn't include my ParamsArray.ext file in the mission folder, but was calling it from the des.ext - that's what screwed it up. :o

Share this post


Link to post
Share on other sites

Please sign in to comment

You will be able to leave a comment after signing in



Sign In Now
Sign in to follow this  

×