Mission Fails to Load

mongoose

mongoose

SOH-CM-2025
Had this issue b4 in the past. Steps taken without success
1. Deleted AppData folder and redone.
2. Removed missions folder and substituted with similar one from another working TOW II install.

So besides these steps, what else could cause the problem?
I should add that I can go to the QC and missions and afterwards the install will revert to normal initial screen.

mission prob.png
 
mongoose said:
Nope. That wasn't it,; even deleting all the mission files, not folders, didn't do the trick.
Click to expand...
Sorry for the troubles ,even though i don't have a clue. Hope you get it sorted out. Please let us know what you did to fix this issue. Regards, Scott
 
It is definitely a mission problem that i do know. Wish i could help. Take care buddy , and i hope you get it figured out buddy. Regards, Scott
 
Well, I have loaded all the missions from the offending install to a similar install and no problem. AFAIK all facilities and buildings are the same in both. Also, as I said, I can start a mission or QC, and when it ends, I'm back to the normal staring screenshot of the airbase used in that QC or mission.
 
It's something to do with an aircraft or more. I may have deleted one called for in a mission. Yet to specify which but will do! (made a new install and initially deleted its aircraft folder and replaced it with the one from the problem; then problem re appeared)
 
I have the same problem with some missions,when i remove all facilities from the mission file the mission runs,my question is where are these missing facilities.
 
alcanallen said:
I have the same problem with some missions,when i remove all facilities from the mission file the mission runs,my question is where are these missing facilities.
Click to expand...
So removing facilities from the mission file makes it work?? I assume you check if these facilities are in your Facility folder, if not that would be a problem.
 
I'm finding interesting things about this issue while using a parallel install. It seems removing some aircraft or even one can cause this problem, even if I leave CFS3 even without that aircraft being the last to fly. Putting it or them back seems to solve the problem. Working further on the issue; it might be to do with a certain amount or overlap between various versions of that aircraft(s), not that that issue is showing up like duplicate m3d files.
 
So problem solved, but not without notepad++. The offending aircraft in this case was a He219AM2; we have also a TOW_He219A-0_M2_G9HL (and in fact a ETO_He219A_M2), all showing historical changes or improvements in the ac with code G9HL. Deleting He219AM2 was causing the problem, so I used notepad++ to search in ALL files for any occurrences, and found 2 outside of the ac folder. One was 2 cases in the frontend.xml in the Missions folder, easy enough to change, and one in the cfs3.exe file, which was a mystery to me, and was solved by copying in an exe file from another similar install, a small advantage of having quite a few similar installs.:rolleyes:

Now, there are many causes for the 'mission failed to load' issue, as some people have mentioned, but in this case I really only solved the problem by having 2 parallel installs and deleting some aircraft files which I didn't want. Then a process of elimination., so partially luck but making the point to examine frontend files and see what ac is being used, and then maybe search the exe file with notepad++ if needed.
 
So, a piece of advice after all that is
-Never delete an aircraft which was last used in QC, and probably a mission.
-If you have deleted an aircraft, check if it's still showing in the frontend.xml, if so change those names to another ac; if you have notepad++, which you should have anyway as very useful, search for files with the deleted aircraft name; there shouldn't be any!
 
Another thing you can do is set ShowUIWorld="false" in the game.xml. This should get the game running enough to then select a new aircraft, loadout, mission type and location. Set it back to "true" once you have things running again.
 
James,

In the TOW II installs, if you remember the He219AM2 was used to replace the p47 as the default start up plane. I also deleted the ju88 and me109 and replaced those with a mosquito and lancaster. Therefore an edited xxxxx.exe file was made along with the additions/deletions in planes etc. This is what WOFF did to have their ww1 planes only. Of course when you delete all these planes from the install (P47, original me109, and Ju88) all missions/spawns that call for them need to be removed to. I believe that somewhere in a sticky or a post that I made over a year ago documents this process....IIRC. I did this again on TOWIIa that I have as well and it works just fine. :ernaehrung004: This process can be repeated for the Korean updates too, if someone wanted to.

Pauke Pauke
 
NachtPiloten said:
James,

In the TOW II installs, if you remember the He219AM2 was used to replace the p47 as the default start up plane. I also deleted the ju88 and me109 and replaced those with a mosquito and lancaster. Therefore an edited xxxxx.exe file was made along with the additions/deletions in planes etc. This is what WOFF did to have their ww1 planes only. Of course when you delete all these planes from the install (P47, original me109, and Ju88) all missions/spawns that call for them need to be removed to. I believe that somewhere in a sticky or a post that I made over a year ago documents this process....IIRC. I did this again on TOWIIa that I have as well and it works just fine. :ernaehrung004: This process can be repeated for the Korean updates too, if someone wanted to.

Pauke Pauke
Click to expand...
I'll get back to you by email, but I had to delete He219AM2 because. AFAIK, it caused problems with TOW_He219A-0_M2_G9HL. Maybe we need to choose another aircraft as the default setup, such as a Bf110?
 
You must log in or register to reply here.
Back
Top