mooshim Posted June 2, 2011 Posted June 2, 2011 Have tried start from ramp, airstrip, turning point... Most bizarre error.. been looking around in the manual... I wonder if this is a bug I haven't seen spoken of. Thanks, Moosh [sIGPIC][/sIGPIC] Win7 | Intel Core 2 Quad | Q8400 @ 2.66GHz | 2.67 GHz 3.37GB of RAM 60gig Samsung SSD| GTX 570 "Operation: Bull by the Horns" "Bull Run 2.0"
hreich Posted June 2, 2011 Posted June 2, 2011 I had the same problem...i think that your loaded mission file is corrupted (i had same problem when editing waypoints and loadouts in campaign mission)...After I copied original mission file, it was fixed... [sIGPIC][/sIGPIC] Pilot from Croatia
MadTommy Posted June 2, 2011 Posted June 2, 2011 I have you tried the obvious and reloaded the DSMS page & checked you do have a loadout on the plane. May sound obvious but it has to be asked. i5-3570K @ 4.5 Ghz, Asus P8Z77-V, 8 GB DDR3, 1.5GB GTX 480 (EVGA, superclocked), SSD, 2 x 1680x1050, x-fi extreme music. TM Warthog, Saitek combat pro pedals, TrackIR 4
Zeke Posted June 2, 2011 Posted June 2, 2011 I had the same thing happen to me last week, I just restarted the mission, but afterward I think I should have restarted the IIFFCC to see if that would have worked.
Toadster Posted June 2, 2011 Posted June 2, 2011 Hi guys. as MadTommy asked, did you press the "Load All" OSB on the DTS Load screen on the Left MFCD prior to checking your DSMS page? You will also get this if you changed your weapons load out from the mission default and would have to reload the DSMS. No need to reboot the entire IFFCC stuff really.
Nixon Posted June 2, 2011 Posted June 2, 2011 Yeah I had this happen too. Just had to reload the DSMS 3 or 4 times and it finally showed up.
nomdeplume Posted June 2, 2011 Posted June 2, 2011 Things like that are usually are a result of using 'prepare mission' which causes the game to save information about all your systems configuration, including DSMS profiles and inventory. If you then change your loadout for that mission, it'll still try to use the pre-saved DSMS configuration and things get weird. If you open up the .miz file (it's just a zip file, so use e.g. 7-Zip or rename it to .zip and then use Explorer) you should see some additional folders in there, and one will be called 'dsms' or something similar. If you delete that, I think it'll fix the issue. Back up the mission file first, of course!
Recommended Posts