Jump to content

Recommended Posts

Posted

Ok there is the problem, latest patch, loaded up the update Tornado so Sundowner and I would look it over before we upload it. If you do not mess with the loadouts and just hit FLY. No problems, however if you go to change your loadout then select your wingman to change his, it locks up. Now for the even more weird part, if you just hit fly, exit out the mission, then for some reason you can now change your wingmans loadout without it locking up. The crash log says a the error is in the singlemission.dll. However Ant and I have went through the ini's with a fine tooth comb and still cant seem to figure it out. So we need some ideas......this is the only thing holding up the release of the GR1's....which in turn holds up the GR4's release as well.

Posted

I have been having the same problem. I even tried dropping my video resolution & depth, checked all my drivers, etc, to no avail. I'm using W7, but I never thought about checking the crashlog. I make no promises about what I can find that will work, but I will look again now that I have a starting point.

Posted

I suspect this is a problem since a patch. In SF2V, I had a random 30% crash that mostly happened when I was altering loadouts. One very strange thing was I found some conflicts in the terrain types list. A couple of the same models had different target types, ie warhouse/powerplant etc. When I was bug hunting this problem I never thought of it as it seemed unrelated. However seemed to reduce my issue with this. Still happens every now and then though.

Posted

Ok there is the problem, latest patch, loaded up the update Tornado so Sundowner and I would look it over before we upload it. If you do not mess with the loadouts and just hit FLY. No problems, however if you go to change your loadout then select your wingman to change his, it locks up. Now for the even more weird part, if you just hit fly, exit out the mission, then for some reason you can now change your wingmans loadout without it locking up. The crash log says a the error is in the singlemission.dll. However Ant and I have went through the ini's with a fine tooth comb and still cant seem to figure it out. So we need some ideas......this is the only thing holding up the release of the GR1's....which in turn holds up the GR4's release as well.

 

I remember having it with carrier birds and not so much land based aircraft. :dntknw: Though can't wait for an updated GR4 though, they needed some serious overhauling anyways...

Posted

Though can't wait for an updated GR4 though, they needed some serious overhauling anyways...

 

Well if we don't get this problem solved then the GR4 will not see the light of day. We can't release them like that.

Posted

sounds like a post at 3rd Wire is in order ... and thank the gods I didn't apply that patch!!

 

I just did that....other than that the Sept patch is fine.

Posted

So to be clear, the only issue is changing the wingmens' loadouts, not yours?

 

I'll try testing that out myself to see if any other 3rd party planes suffer from that for me.

Posted (edited)

I just did that....other than that the Sept patch is fine.

 

Fair enough, I've never noticed that issue since I don't fly with wingies that much, or rarely, though I'll check that issue if its a problem with me too.

 

EDIT: Might be just aircraft specific as I tried that with a wingnut (2 x F Super Hornets) and loaded fine, though it loaded the next loadout, which for a CAS mission would have been fine) but loaded fine with no errors.

Edited by EricJ
Posted

So to be clear, the only issue is changing the wingmens' loadouts, not yours?

 

 

Correct, as soon as you select your wingman, it locks up.

Posted

it is definitely loadout related. I removed all the load out entries and I can select the wingman just fine. Now I need to know where the problem lies..

Posted

What really bugs me is that everything works fine on pre Sept installs, also like Dave said , if you just hit fly, exit out the mission, then refly, now change your wingmans loadout without it locking up,

weird or what????

Posted

Well i figured it out. Too many station ID's. Need to fix that.

 

Speaking of loadouts, after the Sept Update the F-105s have split loadout of 1 AIM9 and 1 ECM pod on their outer wing stations. Pre Update it was both with ECM pods.

 

I haven't extracted the 105s data.ini to see what was done.

 

Hurc

Posted

Just copied my Aug SingleMission.Dll into my Sept install & everything now works fine so summat has definately changed somewhere.

 

Same here Sundowner; you beat me to the posting. There's a LOT to be said for back-ups.

Join the conversation

You can post now and register later. If you have an account, sign in now to post with your account.
Note: Your post will require moderator approval before it will be visible.

Guest
Reply to this topic...

×   Pasted as rich text.   Paste as plain text instead

  Only 75 emoji are allowed.

×   Your link has been automatically embedded.   Display as a link instead

×   Your previous content has been restored.   Clear editor

×   You cannot paste images directly. Upload or insert images from URL.

×
×
  • Create New...

Important Information

By using this site, you agree to our Terms of Use, Privacy Policy, and We have placed cookies on your device to help make this website better. You can adjust your cookie settings, otherwise we'll assume you're okay to continue..