mtpiperpilot

Well, I've done all I can to try to get this working again. I have no idea what's wrong. I've contacted the author, and so far no response. Seems like we might be out of luck for now.

Same here. 2.5.6 stable update this past week broke the script. Every time the LSO script audio comes in, I get error messages.

I feel the same way! Well said. Even for $80, for what we get, it's absolutely fair. And I'm not saying I think this is a cheap hobby, either. $80 is a lot of money, but I definitely feel it's well worth it. And when on sale for 20 or 50% off, it's truly an absolute steal. This EA business model is frustrating at times, for sure, but for the most part they dont release updates that critically damage the module or make it unplayable. That's the key. No software will ever be bug free - it only because a true problem when serious bugs make it into the release. But, all that said, I'd still much rather have this system than the "old" method cited, where the software is released and it "is what it is". Maybe it will get an update, maybe not. Here, we all learn, grow, develop, supply feedback and adjust together. Many more viewpoints get incorporated into how the software should behave. How the plane should fly. Gives time for real world pilots to weigh in. Dev team has time to implement things and find workarounds. Etc. There are SO many times the pros outweigh the cons. And we get a much, much better product cause of it. When you're in software development and you have a hard deadline, the product is almost always inferior. You simply cant develop modules like this in that way. We should not ever forget how complex these modules are, and remember that attempting to compare them to past products from different companies is apples and oranges. As far as I know, no one has ever attempted something as complex as the modeling in DCS aircraft. There are even many documented cases of real world Hornet and Viper drivers, for example, who are in awe of DCS's aircraft fidelity - stating the overall experience is FAR better than the military sims they have. Imagine that! BTW Even the full motion sims for the military and airlines have some pretty crazy bugs. I encountered some really odd things in my own flight training. And let us not forget that the ACTUAL aircraft have software bugs, too. DCS is doing just fine. Personally, it's absolutely incredible the depth of coding and interconnections. I've done some coding before, and let me tell you, the amount of work that must go into just a single module is mindblowing. It's not just art time and coding. It's research, study of systems, testing, etc. It's just crazy they're able to do all this with such a small team. Hats off to each and every one of the ED team members! Anyone who disagrees either doesnt comprehend what's involved or they're just in a bad mood. Both things happen to the best of us.

Noticed tonight that with the speedbrakes extended, the underwing stores clip into the control surfaces as they're deflected. This wouldnt happen in actual flying too often, but I'm guessing there should be a limiter?

I concur there's an issue with the spool time. It's a little longer than it should be (6-7 sec, when it should be 3-5 sec), and this is according to Hornet pilots, NATOPS, and real life videos. No wonder it's so hard to trap on the boat. Here's an interesting video. Engine test, and then the pilot brings both throttles back to idle, and then immediately full burner. Takes 3.58 seconds for the right engine to get to full AB, probably because it was still spooled up from the test. And 5.54 for the left engine, which was truly at idle.

Sorry, danidr, just saw you had asked me a question in your previous post. But it's interesting and hopefully a lead for ED, if they're investigating since we've heard nothing but crickets on this. Full screen definitely makes the gameplay more choppy for me as well.

I dont believe it affects the new Supercarrier DLC - I dont have it installed.

Daniel, I definitely appreciate the input. There's hardly any CPU usage, strangely. It fluctuates between 12 and 30%, sometimes reaching 50%, but does appear to be utilizing all cores. BTW, when sitting idle, the GPU and CPU temps are about 32C and usage is 1-3%. Attached is a screenshot of task manager and the MSI system monitor. This is flying in the Hornet in the Black Sea "Free Flight" quick flight at about 2,500 feet AGL, framerate locked at 30 using autoexec (in an attempt to give the GPU some breathing room - not capping it will also introduce more stutters). The settings I'm using are also attached. So this would be a best case-scenario for me. What I have found to be the best balance of visuals and performance. The GPU generally is near 100% usage most of the time. If, however, I use the fullscreen option via the tickbox in the settings, overall framerate is about 25% lower, and GPU utilization bounces between 60 and 80% utilization, sometimes dipping down to the teens and then shooting back up, (presumably causing the stuttering). Oddly it doesnt appear to matter what the load is on the hardware, meaning if I tank all the settings, it will still behave this way. This is the only game/sim that I have that acts this way, and, more importantly, it never did before 2.5.6. I have AA and Vsync turned off in-game, and enforce them in the Nvidia control panel, along with max pre rendered frames set to "1", which also helps smooth out micro-stutters, but not the big ones we now have in 2.5.6. Here's my computer specs: https://forums.eagle.ru/showpost.php?p=4358864&postcount=349

I've been experiencing lower frame rate and stutters along with lower GPU utilization in full screen mode in 2.5.6, that wasn't the case in 2.5.5. More of my experience here: https://forums.eagle.ru/showthread.php?t=263428&page=37 2.5.5 seemed to have more consistent and steady GPU usage overall, whereas 2.5.6 has sudden dropoffs and associated in-game stutter.

I'm also having something similar happen, but the difference is banked, straight and level, it doesnt matter. I get stutters regardless. I've pretty much ruled out graphics settings - even with everything all the way to the left, it still happens, despite a crazy high frame rate. I have an older machine, but can still fly with medium/high settings and framerate locked at 30fps. For me, it seems like the factors involved are MSAA - will amplify the stuttering to an unplayable degree. Vertical Sync doesnt seem to affect the stuttering frequency at all...on or off, it's about the same. The other factor that appears to reduce both GPU utilization and framerate, and increase stuttering, is going to full screen mode (using the checkbox in settings). Alt-Enter no longer appears to do anything at all except flicker the screen in 2.5.6. Meaning, you can hit the key command but it wont actually take you in/out of full screen. But, for me at least, unchecking the fullscreen option and running boarderless fullscreen also increases framerate, GPU utilization, and reduces stutters. None of this was the case in 2.5.5. I had fluid gameplay, with few stutters, and could use Alt-Enter. More info from my experience, here: https://forums.eagle.ru/showthread.php?t=263428&page=35

Speed-of-Heat, As far as the pre-load slider, I've also been messing around with it. I'm not sure it really does much that I can notice, though. I had it set to 60,000. But setting to 15,000 and conversely 100,000 doesn't seem to affect gameplay or memory usage.

I think we're on to something here! Only....it's backward from expected behavior. I started experimenting with full screen. I noticed when I'd ALT-Tab, i'd get significantly higher framerate and higher and more steady GPU usage, and the 1 second stutter would disappear completely. It still stutters occasionally, annoying but not unplayable. Then, I noticed the "Fullscreen" checkbox in the Display settings was on. I thought...why not try to turn it off and see what happens. This is where it gets strange. After unchecking the box, the gameplay is smooth and high framerate. So, when I thought I was Alt-Tab-ing to fullscreen, what I was really doing is going to borderless window mode! I've even been able to increase settings a little bit, and still maintain 30fps in moderately challenging scenarios. So, for me at lease, full screen limits frame rate, dramatically curtails GPU utilization and introduces a stutter. Never would have thought!

I've been paying more attention, and it seems the stutters happen in approximately 1 second intervals, and when low to the ground and near bases/detailed environments. Even though I'm not maxing out my CPU, RAM, or GPU (I was wrong - it doesnt sit at 100%, I've seen it get to 99%, but it fluctuates from 70% to 90% most of the time in game). I've read a few accounts of similar reports here and on Steam forums, but none resulted in any real conclusion.

The power settings seem fine. Other sims/games dont have this issue, so I dont think something inadvertently changed. I set the DCS.exe to High priority, and tried lowering the resolution, and they didnt help either. Thanks for the help though! I'm also out of ideas... I guess I'll wait to hear what ED says.

I tried turning off my realtime protection, but it had no effect. Still stuttering. I had hopes for this one!

When idle, the GPU sits around 1 to 3% and the CPU 1 to 4% or so.

I figured out how to fix this issue, for anyone who's interested. Navigate to: DCSWorld\CoreMods\tech\USS John C Stennis\Textures And copy these three files: Vodostok_Base.dds Vodostok_Base_RoughMet.dds Vodostok_Normal.dds And paste them here, overwriting: DCSWorld\CoreMods\tech\USS_Nimitz\Textures Not sure what happened...but this appears to restore the correct textures.

Thanks for the tips, Speed-of-Heat. Unfortunately, I've tried those to no avail. As I said in the original post, even if I reduce my settings all the way, on every slider, I still have the stuttering, and I didnt with 2.5.5 even on mostly high settings. I get good enough framerates (I find 30 acceptable), so the stutter is a mystery. Also, by capping my framerates, I am attempting to give the GPU some overhead - without the cap I would get about 10-12 frames higher. So, I dont think the GPU is maxing out (but it's close).

Stutters galore Well... I've discovered the frame rate in 2.5.6 is very similar to what it was with 2.5.5, but now I get constant micro-stutters every second or two, with massive long stuttering at random every 10 seconds or so. Worse closer to the ground. This did not happen with 2.5.5. It was silky smooth with the same settings (attached settings grab). My frame rate is locked with an autoexec file at 30 fps, and even above Las Vegas I get 30 fps in the Hornet, and medium-high settings (see screenshot). So I know the hardware power is still ample. Granted, my computer is older, but I will have to make do with it for now. It's an MSI laptop - GT70 running windows 8.1, with an i7-4810MQ @2.8GHz, 20 GB ram, Nvidia GTX 870M card (3gb dedicated), and the drive DCS is on is a Samsung EVO 860 1TB SSD with more than 25% free space (separate drive from OS, which is also an SSD). I tried updating my Nvidia firmware, but driver 425.31 is the last/newest driver for my card. I identified any MSAA setting other than OFF introduces even more and aggressive stuttering. SSAA and SSLR introduce a very low frame rate. So I'm enforcing anti-aliasing with Nvidia Control Panel, set to FXAA On, Override, 8x. Looks pretty good in-game, and almost no performance hit, but screenshots have no anti-aliasing (bummer...). Also set Nvidia power management mode to "Prefer max performance" and set Max. pre-rendered frames to "1" - this seems like a sweet spot. Helps a little...not much. I feel like I've tried everything... -Disable Hot-plug devices. -Turn off shadows and various tweaks (like that graciously made available by Mustang) to disable ground shadows. -Disable autoexec file/frame rate limiter. -Ensured via task manager that all cores are set up to be utilized. -Deleted the MetaShaders2 and fxo directories -Turned off Nvidia control panel overrides for anti-aliasing, etc. -Steam Verify Cache None of these things helped. Out of curiosity, I set my display settings to the LOW preset, and still had the stutter. So that indicates something other than graphics settings. When I'm flying, my CPU usage is around 30-50%, and my GPU is 100%. I wish I could roll back to 2.5.5 but I dont think Steam allows that. I'm baffled why 2.5.5 was smooth (and most previous versions of DCS, for that matter) but 2.5.6 is so herky jerky. Of course this happens days after I buy a bunch of modules in the 50% off sale.... Thanks for any help/ideas! Brandon

The core Stennis (old version) now has corrupted tie downs across the entire deck, with the new stable build 2.5.6. Anyone know where the texture is located, and how to remedy this? Update: the elevators are unaffected by this bug.

Hi Blech, You are indeed correct! Setting up the train in the mission editor, and it's visible. I'm very surprised how highly detailed it is! I wonder if there's a way to edit a config file somewhere to make them the default on the NTTR map, and not the Russian ones? Thanks for the help finding how to access it!

Just bought NTTR, and have been flying low level marveling at the detail. But I agree...this is really odd and immersion breaking. Has there been any updates on this? Even if it was a licensing issue, I wonder why they didnt just remove the markings? I looked for a newer thread but didnt see one.

That works perfectly! Thanks again! :)

Blooze, thank you so much for that info! I'll give it a go tonight. :thumbup:

Hello everyone! First time poster, though I've been around since the LOMAC days. I've had the DCS A-10C sim for quite a while, but took a break from flight sims and am recently getting back into it. I realized that DCS:World looked the better way to go, so I downloaded and installed from Steam. Everything seemed good up until last night when I realized that the A-10C skins change, depending on zoom level in the F2 exterior view. This only seems to happen in the training missions for the A-10C. See below: I recently purchased a really nice high end MSI laptop, and now I can run DCS with most everything maxed out and still get 45+ FPS. I have the MSI GT70 894 - http://www.msimobile...age.aspx?id=453 with upgraded SSD and Ram to 20gb. All windows updates, firmware/graphics card updates, and steam/DCS updates are current. I'm at version 1.2.16.39472 of DCS: World. I have no problems with any other sims/games, and my computer recently passed a RAM/GPU stress test. Strangely, this problem doesn't appear with the dedicated DCS A-10C sim, at all, which is at version 1.1.1.1. I've tried verifying the cache on Steam, no change. I've not modded DCS: World at all. I've searched this forum and the web and haven't found anything that points to the cause. Any ideas? If I were to guess, it seems like an LOD issue? But I'm certainly no expert. Thanks for any help! Brandon