VAF [136] Striker

You can delete this entire thread BigNewy. It turns out that I had a memory module that most likely wasn't seated in the slot totally or had a tiny bit of hair or dirt on the connectors. I upgraded to 32GB but when I went into the computer properties it was only showing 24 so somewhere between me installing the new ones and yesterday, one of the modules stopped functioning. So I took them out, blew out the slots and cleaned the terminals and everything is working fine now. The problem had nothing to do with DCS or any mods.

I forgot that I had them in there. I removed the two that we've been playing around with, the A-7 Corsair and the F/A-18C from the Stingers. How do I know what event to look for, there are thousands of them. I did do a DCS repair and I just updated my Nvidia drivers. I'll let you know what I find out.

Removed the mods and did a repair but still crashing. Updating drivers now to see if that helps.

Started running the "Enemy Within" campaign and just started getting the Blue Screen of Death. I do have a couple mods that I use, one being the RWR mod and the other being the Su-25T cockpit texture mod.

Look at the 4th post down from Chizh, second paragraph. They have already mentioned that they're going to merge 1.5 and 2.0 some time soon. Wags had mentioned that it should happen some time in January but they didn't give a specific date so it's kind of open at this time. The biggest task they have right now is upgrading the Caucus's map for World 2. http://forums.eagle.ru/showthread.php?t=151478

We've been using CTLD but have found that as soon as one soldier is killed out of a group the soldiers just sit in the same place forever. We've even set them as immortal but every once in awhile one of them still dies and then the same thing happens. Anyone know how to overcome this problem?

Thank you for posting that! I'm sure it will help us out a lot.

We set up a simple mission where we drop off troops using CTLD but want them them to move to a specific zone. I've tried using waypoints but since the group is essentially despawning when you pick them up and respawning when you drop them off, the waypoints become invalid and crash the mission. I haven't really been involved in using MIST yet but I noticed that there's a GroupMove option built into the script. What we want to do is drop them off, have them move to a specific trigger zone and hold there for a timed amount, say 5 minutes, and then move to another trigger zone for extraction. Is this something that can be accomplished with MIST or is there something else that works to accomplish this task?

They have a very short range, about 6.5 miles. They're easy to detect on RWR so it's best to not fly directly over them. Anything radio/optically guided is difficult to evade for the main reason that chaff and flares are not effective at all. This article explains how they work. 2K22 Tunguska

OK, that's officially weird. We were all experiencing the exact same problem but it's working fine now so I don't know what the problem was. We've run the same mission on the previous version of 1.5 and it worked perfect before as well. Maybe it was just a fluke.

We were in for two and a half hours last night so the track file is way too big but I'll run it again as a short instance and post the track file.

All of the above are broken again in multiplayer. We were able to get it to work eventually but we get no acknowledgment from the ground crew or from the tower either for that matter. Looks like all ground operations are messed up again since the 1.5.2 patch.

I would like to see maps that are only usable in a dedicated server environment that are free to use for the server. Right now our only choice is to purchase the NTTR map if we wish to run it on our server and everyone in the group has to purchase it as well. Since the server would be running in a non-client mode, it would be a very good way to promote and encourage people to purchase the maps in the future without forcing the people that run servers to have to own it.

Nope, haven't been able to get it to work.

Has anyone figured out how to use ADF in the A-10C? I know it's a primitive system and really for a last resort. I would like to know how to use it though. I've studied the procedure and the setup on page 611 but can't get it to work. It should be UHF 261 and VHF 156 for Senaki unless I'm using the wrong freq.

Has anyone figured out what the optimal settings are for running a dedicated server are yet and could you post your settings here please? I've gone through and optimized everything I can think of but I'm sure that I'm missing some tweaks. Thanks!

It's working now. I had an extra DX11 capable video card. I swapped it out this morning and it's working perfect. We'll do some testing for connection with our squad members this weekend. Thank you for your help. By the way, I was a little concerned that it wouldn't run on the older quad core processor but it runs absolutely fine. I do think that there's some optimizing that needs to be done though because I'm still getting a little stuttering but it's much better now.

OK, I understand what's happening now. It's not that the computer has DX11 it's that the 4300 is only capable of running DX10.1. So it looks like I'll have to get a new video card and upgrade it. Thanks for looking at the thread.

I sent you a private message but it is running DX11.

Dell Vostro 420 LGA775 Intel G45 Chipset 8GB DDR2 System Memory Intel Core2 Quad Q-9650 3.0 Ghz Windows 7 64 Bit (all latest updates) AMD Radeon 4300-4500

Excellent article Razor, thanks for finding and sharing it.

I can verify that since this latest patch (1.5.1.47285)that the stuttering is mostly gone and that the problem with the trees shimmering and semi-transparent vehicles in BHOT and WHOT mode have been fixed!

Won't work for me at all even since the update.

thanks for the suggestion and I can understand why since my listed spec's are for Nividia but our squad server is running AMD video. All of the 3D is turned off though.

I thought that was supposed to be included with the install package. Anyhow, it didn't fix the problem. It looks like it's a DX11 issue related to shaders. I'm including the new log along with the .crash file.