[Plantoid 1]

Hi all:

My buddy called and tipped me off about this...

I loaded one of his missions based on the Ardennes Winter map. I can call up the mission in FMB but, when I try to Play from there it won't let me. When I make a change and try to save it, it won't let me. When I try to Exit, it won't let me. I can exit FMB by answering "No" to the 'Save current mission' popup. I can play it from Single Mission on the main menu and, if I move it manually to Net/Coop I can play it from there too - the original version of the mission only.

I tried another winter mission based on the Gulf of Finland Winter map. The same exact issues.

We have the following map downloads:
AAA_map_pack_1_2
dlv_Phillipines_v2_0
dlv_sinai
LAL_Okinawa
mrz_Malta_Map_v1_3
NTL_Darwin_Small
RD_Malvinas
vol_ItalyAfricaGreece_v1.0
vol_Sardegna

If this is the wrong place to post this can you point me to the right place?

Thanks in advance

edit: I just spent the better part of an hour going through a bunch of maps and found the following maps have the same issue:
Ardennes Winter
Balaton 2
Moscow 1
Murmansk
Stalingrad 1
Gulf of Finland 2
Online 10a Winter
Online 1 Winter
Online 2 Winter

In all cases a mission seemd to save ok - the file name came up at the bottom left of the screen as normal.

When I finally exited and went to the Missions folder to see if the missions made it that far, I only find the file 'filename_ru.properties' the '.mission' portion is missing.

Hope this helps sort this out

Great days all.

[delvpier]

Known bug... but for unknown reason :roll: ( nobody has found yet an explanation...)

There is a fix : delete the following line in bldconf.ini

(builder.PlMisDestruction)

and you'll be able to save on any map :wink:

[Plantoid 1]

delvpier:

Thanks a million man! That's the ticket. We can now get back into the frozen tundra.

Great days all.

[WWSandMan]

Known bug... but for unknown reason :roll: ( nobody has found yet an explanation...)

There is a fix : delete the following line in bldconf.ini

(builder.PlMisDestruction)

and you'll be able to save on any map :wink:

Just wondering... does that 'fix' disable the destruction brush then?

I have also had issues with not being able to save some maps. Some of those issues I've been able to work around by removing VPMedia's map texture update mod.

[Guest]

I think it does, Sandman....you'll find you can't use the destruction brush in FMB with that line deleted.
You can also disable the line by putting // in front of it.... :wink:

[Plantoid 1]

Sandman:

What mod are you talking about - the VPMedia map textures? If I have it, how can I disable it?

We had a problem flying missions last night on the Gulf of Finland Winter and Ardennes Winter maps. Some of the smoke columns placed on buildings either seem to have moved, or buildings have disappeared. The missions were made a long tima ago and my buddy can't remember where every building was placed but was sure he'd placed them where the smoke was; in all cases it would have made sense.

Great days all.

[Fisneaky]

I do know that if the map was created using FMB+, and uses objects that FMB+ unlocks (ground plates etc.); then you can't save it with standard FMB.

[delvpier]

I do know that if the map was created using FMB+, and uses objects that FMB+ unlocks (ground plates etc.); then you can't save it with standard FMB.

No... when a new map is "not saving mission file without deleting the line in bldconf.ini"... it happens at the start.... before any change in FMB unlocked or FMB+ unlocked... with a nude map without any object (generic or modded) or any modded texture...

Nobody has found the reason until now... I tried millions of things to understand this bug... but at this time, nobody can't say why some maps are "saving" and some others are not ??????

Sometimes, you get a not saving map and when you try to make it with an other size (ie 100 pixels more in each side) it gives a saving map... Is this related to the size ??? I don't know because I can't get valid rules to transform a not saving map to a saving map by changing size...

Sometimes I thought it was related to differences in treatment of grey colors of map_c between Photoshop and Gimp... or to differences between various map_c tools... but again, I can't get rules...

So at this time it remains an open question... if someone has a real answer, PLS SHARE :wink:

[Monty27]

This sounds to me like the old 'Static.INI' problem. You need to update your Static.INI so that it contains all of the new objects that the map is calling for, then it should be OK.

Fabian Fred's Static.INI seems to be the best one out there, the most complete. He posted it on a similar thread discussing the same problem with the initial release of CanonUK's Channel Map.

[fabianfred]

I do know that if the map was created using FMB+, and uses objects that FMB+ unlocks (ground plates etc.); then you can't save it with standard FMB.

just to avoid confusion...I think Fishsneaky meant to say ...if the MISSION was created using FMB+...rather than if the MAP was created

as Monty27 says...I probably have all objects on my static.ini (and a few extra ones not released)

[Fisneaky]

As you say Fred. I should have said mission.

The only other time I've encountered any problem other than missing entries in static.ini was trying to modify a mission created in FMB+ (using some ground plates ) just using my unmodded install. Missions are playable and the extra plates are shown in-game, but the mission is not editable.

Possibly it's connected to actors.static file, but I don't know what was put in the mission or if there are any other mods involved that I don't yet have.