• There seems to be an uptick in Political comments in recent months. Those of us who are long time members of the site know that Political and Religious content has been banned for years. Nothing has changed. Please leave all political and religious comments out of the forums.

    If you recently joined the forums you were not presented with this restriction in the terms of service. This was due to a conversion error when we went from vBulletin to Xenforo. We have updated our terms of service to reflect these corrections.

    Please note any post refering to a politician will be considered political even if it is intended to be humor. Our experience is these topics have a way of dividing the forums and causing deep resentment among members. It is a poison to the community. We appreciate compliance with the rules.

    The Staff of SOH

  • Server side Maintenance is done. We still have an update to the forum software to run but that one will have to wait for a better time.

combat flight simulator assertion failed error?

D

dmaloof

Charter Member
Hi, I have a modded eto 1.31 install that keeps giving me the following error:
combat flight simulator assertion failed error. When I clikc abort or ignore, it exits to desktop. All id id was add some planes to aircraft folder and weps and pylons. last thing I did was selecting a North Afrika fw-190 so i could fly off italy and when I clicked on dropt tank 3001, it froze. Now my isntall wont work. Any advice? I already delted usiel file but no go there.
 
Are the required weapons files in your weapons folder? That freeze-up is typical of when you try to load an aircraft with weapons (or pylons - check there too) that are not available. Normally, deleting the uisel file will get it working again, but it'll lock up again next time you come across any aircraft with missing elements. That also happens a lot in campaign/mission mode, when aircraft spawn. That, going by the message you're getting, doesn't appear to be the problem...

I did have something equally weird with the effects.xml once. Problem is, I can't remember for the life of me what was causing it. But I seem to remember it happened every time I used an old beta I-16 (NOT Dancat's!). Deleting the aircraft was the first step, but I have a nasty feeling that I had to reinstall the lot...
 
Hi, found a solution. i copied a default or unmodded effects xml(luckily I have a virgin install) and it seems to work. keep ya posted.
 
You must log in or register to reply here.
Back
Top