Dr_Arrow

I've been also playing with the new patch - Caucasus stock/2.5OB (DCS/2.5.0.15184), and yesterday I experienced two strange freezes during a mission. The mission was stuttering from the beginning, than it un-choked and ran absolutely fluently for a while, then began to stutter badly again, although I have good FPS between 45-60 with VSYNC. In half of the mission the sim froze completely, sound was running - I waited for 3 minutes and than it unfroze, stuttered for 10 minutes than it ran again nicely after that it again froze for some 15 seconds and after this ran again nicely till the end. I am attaching my dcs.log file, maybe it can provide some interesting information. I just cannot find any systematic explanation, because sometimes the sim is running flawlessly and other times it stuttering and freezing, with no change in settings or configuration. My system config is: Intel i2600K at 3.4Ghz, 16GB DDR3 RAM, Gainward NVIDIA 1070GTX, 250GB dedicated DCS SSD, 250GB Win 10 64 bit Intel SSD. OB2.5freeze.zip

I've had good FPS with 2.2, mostly having it at stable 60 FPS VSYNC with my config NVidia GTX1070, dedicated Samsung SSD for DCS, 16GB DDR3, Intel i7-2600K@3.4Ghz. With 2.5 Caucassus I got bad stutters that everybody is talking about here. I've had good FPS again and tuned my graphic settings for 50-60 FPS, but no matter what I did I could not get rid of the stutters every 3-5 seconds and sometimes freezes for some 10-15 seconds, I tried everything - affinity tricks, sync tricks, driver reinstal, DCS reinstal, repair, MSAA tweaks, Shadow tweaks, FOV tweaks, killing all win processes, deleting caches, settings, disabling ethernet, different Nvidia settings, observing GPU loads (at 80%), processor loads (30-40%) etc. Always when I thought I solved it, the game has shown me that I did not and most of these tweaks were just placebo at first. The only real thing that has indeed helped me after all that exhausting testing, tweaking and nerves was disabling shader cache in NVidia settings with 391.01 driver. Now I get mostly 60FPS with smooth gameplay, I do not know, but it might helps someone, try disabling the shader cache, it puts some more strain on the processor but for me DCS is more GPU heavy.

I do not know if it has already been posted in this thread, but this video is really interesting not only in description of the magic carpet landing system, but general ship landing techniques and how magic carpet improves it, might give someone a better understanding of what's going on:

I know removing the canted pylons would cost a lot of money, but isn't it really performance wise a big gain, moreover when projecting the future life of super hornets in decades? I just cannot understand that they can live with such apparent error, which compromises performance and costly improving it by using CFTs and other measures, while leaving the pylons canted. This also can't be good for frontal RCS.

Will Block III still have the canted wing pylons?

AFAIK, cannon does not need laser for guidance, to fire the cannon you need slant range measurement (with laser)/estimation (without laser). Estimation can be done with damaged laser, the system will calculate range of the target using other parameters, but it is a lot less precise than laser ranging. So you can hit targets with cannon without working laser, but range will be only estimated, so less precise.

Home Fries: this is it, I somehow missed that you need to define modifiers as well within DCS. Thank you very much.

I cannot get shifted commands working with 2.5 L-39C with warthog, S3+combinations do nothing, is it a problem with 2.5 version or am I doing something wrong? All other commands are working, the shifted ones do simply not. Thank you very much for an answer.

It would be nice to have this finally fixed with 2.5, seems not like some difficult bug to squash.

Yes, it is definitely yellow, outer environment will make it look as different colour - that is normal, in my opinion it is a perfect representation of the real thing.

Moreover using air-brake disengages PAC during gun runs. Setting the engines to idle is more than enough for the slow hog during steep dives.

It seems that it is not much used in RL, because of poor precision and certainly not usable against small targets. This is what a real Warthog pilot had to say about force correlate for Mavs: Q: How often and in what situation would you force correlate a Maverick? A: Large, poorly bounded target. Avoid at all costs.

As I am learning A-10C and have watched many videos as an experienced BMS F-16 virtual pilot I've always wondered why the hell are people launching mavericks in tutorials with flashing cross meaning it will probably miss, now I know - I hope it gets fixed.

Thank you for the heads up, keep up the good work :-)

It is still not corrected in 2.2, with deferred shading on - floodlights do not illuminate the cockpit at all :(

What I miss in DCS and also in BMS and what is quite an important factor during SEAD are false emitters. In BMS you see one SA-2, but as I've read (Hampton, Rosenkrantz, etc.), in reality your HAD or RWR would be cluttered with many false emitters so that it is often hard to discern, which one is the real one, though newer systems might be better in suppressing them. Moreover I know that Russian SAM systems are all able to simulate launches. All this deception techniques are also missing in BMS.

Weta43, will any other small fixes to Su-25A be done in near future: i.e. CCRP sometimes not working, reversed engines animation, bort numbers problem, laser stabilization problem. I know it is an old plane and not much attention is put on it, but I think that these could be easily fixed and be much helpful for community flying this famous aircraft. Thank you very much.

You are not flying level, but descending here.

:huh: This is totally disappointing for me. I have unfortunately shelved DCS until 2.5 is out - in any state or condition. I really do not know what is the point to release new modules (Harrier, F-18, Yak, etc) for 3 different versions, which have different maps, technologies and bugs and do all the bug patching. In my view it is a big waste of resources and fragmenting the community as well as putting away new customers. This has to be developer's nightmare and I cannot understand that ED has remained in this state for two years and unification is nowhere near it seems. Just roll out 2.5 even in unfinished Caucassus state, patch it up in frequent incremental automatic updates, afterwards drop support for 1.5xxx and life will be much better for everyone - developers, module producers, community and potential customers.

Su-25A has a yaw damper system, upper part of the rudder works as the yaw damper. But I am not sure if it is ASC, you can notice it is working when you quickly move rudder the upper part of the rudder moves in the opposite direction to compensate for possible oscillations.

I'll get it, it will make a nice progression - start in Yak-52, move to L-39 then to Mig-21 and further...

Even though the F-18 is not using AP for aerial refueling, in F-16 when you open refueling doors the FLCS changes control gains, so the can have much more precise control and the aircraft is in result much less responsive. The same might go for F-18 or basically any FBW aircraft, which is changing internal control laws (including damping) according to flight situation/conditions (ground, landing, refuel,etc.).

I suggest to look into this thread - I haven't tested it in the last version, but altitude hold AP and its related modes work well only when the SL baro pressure on the map is set to 760. Basically the altitude hold AP does not use the reading of the on-board altimeter but uses some own altimeter set always to 760 (I think it is a relict of old modeling when we weren't able to change QNH of the altimeters in FC1): https://forums.eagle.ru/showthread.php?t=150622&highlight=Su-25T+autopilot+bug

I just hope that we will get Caucassus in 2.X as soon as possible so we could finally ditch 1.5x. Having 3 versions of the sim must be a bug-tracking development horror-nightmare for every module producer creating a mess among modules and certainly lowering quality. I am just puzzled that they have kept this going for such a long time ... I personally do not mind if the new Caucassus is not 100%, it already looks so amazing and much better than what we have, just unite the versions please.

I suppose that these were training rounds with inert charge. I am quite puzzled how it managed to shoot unguided rockets exactly in the second when the targeting circle jumped on the vehicle. Automatic trigger on unguided rockets, which are more area/spray and pray weapon does not make much sense.