If someone could figure out how to get the mission builder to stop creating and reading *_ru.properties files instead of the english default *.properties files they would certainly be my hero.
Since installing the sound mod I have noticed the following......
When opening an existing mission in the FMB........ what was before a mission.mis and
mission.properties .....now has an extra.... mission_rus.properties which has been
created
if there was a briefing in the original .properties file it does not get put into the new
one...... if you leave it like this, when you host the mission on-line the other players will
see the blank brief.... and if you copy the text into it from the original .properties file....
they may see the brief in russian...
so.........after finishing your editing in the FMB... delete the mission_ru.properties file
If you are making a new mission in the FMB the file mission_ru.properties will be made
with the text for the brief..... after editing in the FMB....... delete the _ru leaving just the
normal mission.properties and you are OK
Yes, it's a pain to have to go through and change all of your old and future files though. It would be much more simple if the mission builder used the non _ru format files. But hell, if that's the way it is, it's a small price to pay for everything else.
I assume it happens because we use a hacked version of the Russian language exe to start the game. It initiates everything in Russian ie tells every sub-routine to read and display only .ru files.
It's odd that we still have this situation, as I confidently thought someone would have hacked the International exe. by now.
I don't know QTim's nationality, but if he's Russian, perhaps he's just not interested in the English language game. MrJolly might be able to contact him for further info :wink:
only the RU version was appropriate for the modding purposes iirc
I was wondering about this myself. In building campaigns I find this to be a real pain. I can just delete the _ru suffix but had been hoping there was an easier solution.
If you want to modify pre-existing campaigns/missions it is very painful the fact that all the description is lost. I used to modify myself a lot pre-existing missions (changing the mission plane, for example from Spit LF IX to Tempest or from P-51D to P-47D and viceversa) because I want to make interesting comparisons of course...so no the existing description is always useful (just changing the mission name).All this is lost.I tried to add an additional _ru properties file but is simply doesn't work (but even this, to modify MANUALLY all the files of your missions is really a headache).
Can anyone fix this bug please?
UPDATE
-------------------------------------------------------------------------------------------------------------------
BEFORE you install the SOUND MOD you should modify all your properties files into _ru WITHOUT keeping another non "_ru" in the mission folders. So the description can be read now in the FMB.The next update of the SOUND MOD should include an automatic modifier.People are so dedicated here, that I am sure is just a matter of time :lol:
Any pre-existing missions made before the mod...should open normally with their brief readable too...
it is only after opening them in the FMB that a NEW _ru.properties file is produced.... so once you have finished editing....just delete the _ru.properties file....... if you have information there you do not want to lose...just delete the _ru...and leave the .properties in the file name
an easier way to change aircraft without this problem is to use the QMT Quick Mission Tuner utility.... links given elsewhere here....as that acts directly on the .mis file without opening the FMB
I meant any missions opened as single player etc......but once they have been opened in the FMB a new ru_properties file is made which is blank...until you copy the details from the old properties file
I can run 4.08m without losing files, but any with mods disapeer, has the sound mod fix
come out?
has this been fixed yet?
(ie it creating _ru properties files?)