Missions compatibility...

[Pochi]

Hello,

 

I have a simple question : there are lots of missions for DCS A10C 1.1.0 to download but can I use them in DCS World or only missions made for DCS World can work?

 

Do you have any missions to advice for a beginners?

 

Best regards,

 

Pierre

[Druid_]

In theory they should work fine however to be on the safe side I would advise that once you have downloaded any mission which was made in an earlier version to open it in the mission editor and resave it.

 

The main problem with older missions usually occur with slight changes in AI behaviour. Its usually down to the complexity and arrangement of the mission. I would say most missions will be fine.

[Pochi]

Thanks for your answer! I will try that then:)

 

Best regards,

 

Pierre

[Kurgen]

I'm having problems doing the load / re-save thing... I've downloaded Parabellum's "tutorial01.miz", popped it into the mission folder, loaded it in mission editor, gone to "save as", but clicking on "save" does nothing. Even if I rename it or try saving it to a different location, all I get is the save button being pressed, but it doesn't actually save, and the save dialog just sits there. Most odd.

[MadDog-IC]

I'm having problems doing the load / re-save thing... I've downloaded Parabellum's "tutorial01.miz", popped it into the mission folder, loaded it in mission editor, gone to "save as", but clicking on "save" does nothing. Even if I rename it or try saving it to a different location, all I get is the save button being pressed, but it doesn't actually save, and the save dialog just sits there. Most odd.

 

I know you are talking abour A-10, but have had the same problems with Blackshark 1.02 mission ported to DCSW Blackshark 2, can't remember exact fix, but this might help, think the not saving is related to the callsign problem.

 

 

Findings are in BS1.02 to get it ready for conversion:

 

• Need to make sure all vehicles / units are assigned the correct type / class - very common to be incorrect
  
• Ensure all call signs on Aircraft are correct for type of vehicle (usa - enfield1-1, russian - 501)
  
• Fix default KA50 Texture
  
• Fix Player KA50 Slot
  
• Fix Name of Units
  
• Unhide everything
  
• Save Mission
  
• Open Mission File - Delete Options file
  

 

 

Findings when loading the BS1.02 mission into DCSW BS2:

• Open BS1.02 Edited Mission File in DCSW 1.2.x Mission Editor - Try resaving first up, if cant save follow the next instructions.
  

 

• Check and fix callsigns - Blackshark 1.02 is slack at enforcing flight callsigns, ie russian ka50 can have usa callsign and vise versa - so when ported over to dcsw it does enforce them and will not allow you to have a russian ka50 with callsign enfield1-1 for example, must be a three digit number instead.
  
• Fix aircraft Role and advanced waypoint Actions - (Intercept, CAS, CAP, etc) these may change from the original when ported because there are different classes and cause advanced actions to be inappropriate for that role - (You will get error message about this one - Example: transport class, with bombing commands).
  
• Fix Trigger logic - Triggers may be deleted if reference a Unit that is no longer in the asset list or has been renamed in a later patch - (Causes mission to not function as intended), you will have to replace the missing unit and trigger logic referencing that unit.
  
• Save mission file - Having fixed all of the above, the mission should now save.
  
• Run mission in DCSW 1.2.x and test - should work as intended hopefully.
  

Failing with all of the above, as a test, make a backup of your mission, go into the DCSW ME and start deleting the flights one by one and re-saving the mission, you will probably find that once one or all of the flights are deleted, that you can resave the mission, if so then you definitely know that the issues exists within on of the flights group parameters.

 

 

Reload the original mission again, deleted all flight groups except one and check its parameters throughly for errors / mistakes. and try re-saving.

 

 

This is how I narrowed down the issues described, and found it is nearly always the aircraft groups at fault. Best of Luck.

 

 

Cheers, Ian.