Jump to content
🛡️FORUMS ARE IN READ-ONLY MODE Read more... ×
Sign in to follow this  
Milkman

Cannot save mission!

Recommended Posts

I just started working on a mission today. When I try to save, I  click save and choose name and where to save. But then when I try to do the save, a little box shows up that says "Saving of Mission Failed!" I have used the editor extensivly and NEVER encountered this before. It isn't a patch, because I installed 1.91 over a month ago, and have used the editor since.

System specs:

Dell Dimension L866r

Windows 98 2e

Pentium III 866mhz processor

256Mb SDRAM

GeForce 4 Mx420

20Gb 5400 rpm Western Digital C drive

Operation Flashpoint: Resistance v1.91 Final

Everything has the latest drivers installed. I ain't quitting Mission Editor untill this is solved. This mission is important to me. mad.gif

Share this post


Link to post
Share on other sites

I know this sounds impacient, but I need help now!

crazy.gif

Share this post


Link to post
Share on other sites

Could it be that the mission file(s) you already have on disk are somehow marked READ ONLY and the mission editor cannot update them?

Just guessing.

Share this post


Link to post
Share on other sites

Try saving to a simple location that doesn't require long filenames or has spaces in the path -- save to C:\TEST for instance.

I seem to recall that spaces cause problems, but I can't test that right now since I'm not at home.

Share this post


Link to post
Share on other sites

Well its too late to save my mission, but no, it wasnt read only, and I wasnt using the folder and when I tried to save another mission, it saved perfectly.

I guess this is some increadibly retarded glitch that will never be fixed.... mad.gif

Share this post


Link to post
Share on other sites

Hey, I found a solution! Whatdya know?

Apparently, when saving a game, there are certain characters that Opf will not read.

When I recieved the error, I was Trying to save the file as;

</span><table border="0" align="center" width="95%" cellpadding="3" cellspacing="1"><tr><td>Code Sample </td></tr><tr><td id="CODE">Operation: Overhawk<span id='postcolor'>

The ":" is what was causing problems. I'm still not sure why though. I guess you just cant put commas and stuff like that in the mission name... confused.gif

Share this post


Link to post
Share on other sites

That's not a limitation in OFP, but in all Microsoft operating systems since MS-DOS 1.0 -- it's simply not a legal character to use in filenames, since it is used to delimit drive and device names.

Share this post


Link to post
Share on other sites

alright, I understand that, but now I have a question related to Windows XP.

The ":" shouldnt be a limitation in Windows XP because XP dosn't run on MS-DOS? I thought that because supposidly, XP was the first operating system to not use MS-DOS. Is that right? Im not sure because I dont own Xp. sad.gif

Share this post


Link to post
Share on other sites

It's not the first operating system from Microsoft to not use an MS-DOS based kernel -- that distinction goes to OS/2, which initially didn't even have a graphical interface (Presentation Manager).

Anyway, the limitation still applies, regardless of what kernel is used. XP and other NT-kernel operating systems use the colon to delimit drive and device names, so you cannot include them as part of a filename. There are other characters that cannot be used, such as the plus sign, question mark, asterisk, backslashes etc. -- they all have special meanings.

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  

×