Skarp

Please take your time with this one. I love the migs and the love you put into it shows.

I was unable to reproduce the crash so perhaps it's actually something to do with a script pulling info on the weapons or what's on the pylons. dunno but only so much I can do having no experience with scripts or editing mission files.

I loaded the preload mission file drex provides on his discord channel and noticed the issue. after I spawned in the f18 it would not give me the option to load the aim9x on the lau27 at all. so I have to assume it has something to do with the mission file. let me know if you managed to work out the issue.

have you tried making a new mission with the f18. something simple and see if it happens. if it doesn't then it has to do with the mission file itself.

I found it!!!!! So it depends on how many farp pads there are in the mission. In drex's mission you can have up to 70 before it causes the CTD. however when I tried to make my own mission I could have over 70 farp pads? So I wonder if it has to do with the name length of the farp pad that determines how many you can have until you hit this threshold.

I've attached the mission file that also replicates the crash. if you choose the viggen you get the CTD. DynamicCaucasus_1.22_FA-18C-Carriers_ADDED.miz

if you need some help having fun on drex's server here's link https://forums.eagle.ru/showthread.php?t=208608

Some of the instant action missions still load up the harrier with agm Ds

here is a crash log dcs.log-20180831-205652.zip

some unit groups are large and spread out and there are also some player spawned units. Not sure how the data cartridge selects the target. If it's the individual unit vs center of the group.

This issue was not happening on the last release version. This new release version the lau-127 on the F18 is causing CTD issues.

after further testing its pointing towards the lua127 missile rack not the missiles. I can load dual missiles on the lua15 or what ever but the lua127 is the culprit.

Here is a twitch video link of the crash here And I've also attached the track.DDCS-Hardcore_PG_1.0.1_N2-20180827-050610.trk

This crash is back now

looks like the crash is actually connected to the sams firing. dcs.log-20180816-194245.zip dcs.log-20180816-193456.zip

Looks like drex didn't restart the server client for a while and once he did the crashing stopped.

this crash happens often and it's driving me nuts.

same issue dcs.log-20180811-185601.zip

Blue side radars will reveal enemy ground units. This is not so for Red side.

When I set the unit to green in multiplayer often it will not shut down and all the launchers will move except the BUK SR. Sometimes it works if you turn it off right away after spawning one in but once it's on you can't turn it off.

In multiplayer when you jettison the canopy or eject often you will cause a lag spike. Not sure why maybe it is forcing everyone to render the canopy model at the same time.

Not sure the point of this thread. The Viggen is pretty much finished and everything you listed and complained about is dumb. Viggen is amazing.

Still not fixed

I removed the FXO and Meta Shader folder and still getting the crash. any more information you guys can get from us to help solve it? For me it's very easy to replicate.

CTD reloading mission so I fly a mission end it then fly another it crashes. I also did a campaign mission and crashed when I hit quit. dcs.log-20180706-154727.zip