VAF [136] Striker

Just my opinion but I don't think the developers from ED have the slightest care about BMS development and it wouldn't stop them or one of their third party developers from developing their own F-16. This has been discussed before but it's probably based more on what's classified and licensing.

It's just speculation on my part but they added the drop down in the UI for changing languages for each aircraft. So maybe they're planning on doing an English cockpit variation for the Su-25T at some point and for the other FC3 aircraft as well. There is a mod for the Su-25T that changes most of the cockpit to English by Devrim here http://www.digitalcombatsimulator.com/en/files/722567/ I mentioned to him that some of the instruments and labels are still in Russian and he said he didn't have enough info to do everything. This was released back in July. It's an excellent mod and does enough to make the T very easy to operate and it does work with 1.5. I would recommend making a backup of your original textures file first or use the mod enabler.

I use GP all the time for start up. It allows you to power up the systems very quickly instead of waiting for APU or engine generator power, but this is just my preference and I know a lot of people don't like to use it. On the other hand, GP is very helpful when you come in to do a repair. You can shut the engines down and not have to worry about having to align or bring systems back up after the repair is completed. You just start your APU and then engines and you're back up and running again in very little time.

Still crashing. Updated log attached. They both appear to do the exact same thing when I try to run it but I've been trying to run it using the green icon. Just out of curiosity though, I thought ED had stated they were going to do a server only executable for 1.5 or was that in 2.0 only?

Done.

I'm experiencing almost the exact same problem. It looks like a DX Render issue. Trying to set it up on our squad server.

I built a new mission with just a couple objects in it for a simple training mission and it's doing the exact same thing, bad stuttering all the time especially when I use the zoom in. I think that until it becomes official, the only solution for me anyhow, is to just do a full uninstall and a clean install from scratch each time there's a patch. I'm not going to do that though. I'll put up with the stutter for now until the official release is out.

Yeah, it's empty. But an interesting note. I was just on the Mudspike flyin server and it was very smooth. One of the guys said that it could be mission related. I've been using the same mission to test everything so maybe I'll do another mission and see what happens.

Every time they do a patch it gets worse for me so I really don't understand why it's better for you. I installed the latest patch this morning and the stutter is horrible.

I prefer not to experiment around with different settings or configurations. The developers and moderators have stated that they want raw information. I leave it up to them to figure out what the problem is and fix it.

Yeah, that's a hefty drain.

OK, everything was working much better until this most recent patch, 1.5.1.47025, so whatever the dev's are doing is actually making the problem worse. And this is after a clean install. So what I ended up doing is turning the preload radius down to 80,000 meters and trees up to 20,000 meters and it helped a little bit but the stuttering is still present when I zoom in as close as I can get. The stuttering is extremely bad at that point. When I zoom back out it gets better again.

LOL, I can't believe that I didn't have that in the signature! It's a GTX-970 with all the latest drivers. As was explained before, this problem was not happening prior to the patch. I've never seen stuttering like that and I make hard turns all the time. But it looks like it's mostly gone after the procedure I stated.

OK Sithspawn. I think it's running OK now. But I had to completely uninstall it and download the most recent version from the website. I cleaned out all track files and temp files and defragged. Then I installed the latest version but it still had to be updated from the updater. I defragged each time after each step. I think it stuttered a tiny bit in the beginning of a mission but it looked like it was mostly smooth. I'll let you know if it happens again.

I did some reading up on this and it looks like this was started as a solution to prevent Windows from writing the page files to SSD drives and burn them out prematurely. I don't think there would be any benefit in my case as I use spin drives. Also, the problem didn't exist prior to the patch so this is a patch related issue. I'm sure that the developers are aware of it by now and will come up with a solution. It is Beta after all and we're all here to test it out and report what we're experiencing so they can make it better in the long run. I did delete all my track and temp files though and defragged again and it seemed to help a little but the problem is still there.

OK, I did a complete uninstall and then deleted the local files and defragmented the drive. Then, I downloaded the entire package from the ED website and did a clean install. I went in and checked to make sure that there wasn't anything different about the settings in the options. It still stutters, not as bad as I noticed a minor improvement, but still it stutters, especially around large groups of objects like airports and cities. So low level flight is still pretty choppy but it's not bad at 10,000 feet.

Nope, no overclocking here. I uninstalled everything and I'm doing a de-fragment now. After I do a fresh installation I'll post the results.

IRQ's don't inhibit system performance like you're stating here. There's a good article here on IRQ and system specifications here and here. Lot's of other information available if you dig for it. But you can have IRQ conflicts so that's something to look for in the device manager. Anything that's flagged should be looked at for possible conflict and you can also go the the device assignment by IRQ and see if anything is being shared. That could be a problem. Windows is designed to handle a large amount of IRQ's and you can see that in the list. But I do agree with disabling anything unnecessary. I disabled my Bluetooth device because I never use it. You don't have to go crazy and disable a lot of stuff though. Just look for conflicts. But again, we weren't having this problem prior to the patch so this is not a hardware problem. It's something related to the file changes in the patch.

No mods at all but program was updated by the patch system on Saturday and it took about 4 hours and was around 3 GB. I think that the server was quite busy. I'm starting to wonder if some files were corrupted because of how long it took. I may make a back up of my users folder and do a fresh installation from scratch to see if it goes away. But definitely this is a problem that happened after the patch.

Tried this but it did not make any difference. Please note the DCS splash screen appearing and the really bad freeze at about 5 seconds.

I agree with you completely on this. It's not my system either. I was getting excellent frame rates and absolutely no stutter before the weekend update and now it's basically unflyable. So this is definitely an update related issue.

Nope, I posted my specs in the preferences section but it's not showing up for some reason. I'm running a GTX 970 on a Rampage IV Extreme with an i7 Quad Core processor. It was perfect before this last patch. Now it's showing up, go figure. | | | v v v

Fixed! I tried it today and the repair works perfectly now.

Since this latest patch (1.5.1.46722.87), DCS is now a slide show. When I'm turning I get huge stutters, in every module. It was fairly smooth prior to this latest patch. It's not extremely bad in this video but still present. When I first tried this mission this morning it was extremely bad. Also, there's a bizarre problem with the trees rendering properly. There are groups of trees that are dark green that appear late. Most of the duller forested areas are rendered at a very far distance. I've posted the track file.

Disregard this post. We figured out what the problem was.