Hoffster

it is in settings for the L-39 so hopefully soon ™

Part of the lighting bug. https://forums.eagle.ru/showthread.php?t=211607

I thought this was implemented already? Tried it and it won't work. MCG pro handle.

Just an update on this after i made this thread. I reinstalled DCS OB just now to see if things have changed. Fps seems higher than in february and that is great. Apart from the same artifacts i mentioned in the viggen pit, oh well.

The folders will be recreated. try that first and then https://www.digitalcombatsimulator.com/en/support/faq/709/

Try a repair and deleting the folders fxo and metashaders in saved games.

Yes i do want that when it comes out but im sure it will have mining tax from day 1? Surely the current "mining" price will be reduced on the current gen cards. here in Swe prices for 1070,1070ti,1080 are about the same about 550-600+ eur :cry:

Lots of good input here. I pretty much decided on a 8700k. My 1060 6gb will carry over to the new system until a 1080 is not crazy expensive anymore. Last time i fired up DCS was right after 2.5 beta came out in january, and my fps on ground was 25-35 fps slowly climbing to 60 at altitude :( single player 1 aircraft loaded in caucasus. Hopefully some improvements have been made in a couple of months. The DCS itch is real now!

Thanks for the answers. Well i guess from a future proofing standpoint the i7 route is worth the extra cost. And fingers crossed when the 11xx series gpu's comes out, prices of 1080's will come down to at least what they cost new 2 years ago ;)

As my current rig won't cut it for DCS at the moment i am looking into a future build. My i5-4690 has served me well in the past and i was always told that an i7 wont be neccesary for gaming for a few fps gains. So looking at coffee lakes. 8600k vs 8700k will the i7 see a noticable improvement in DCS over the i5?. Running at 1080 an 60fps/Hz? Will be running no OC. Thanks.

Do you have Nvidia control panel settings set to vsync half refresh rate?

One or 2 beeps is not a problem in real life either, it gives you an indication that it is working. For me it does that when rotating properly to the upper SI poles. Just as stall warnings is common on touchdown in real life aviation.

Tried to assign this to my brake handle axis on my stick and was out of luck. Would be nice if this gets fixed. Currently using the stable version. Thanks.

Very much agree to this post. I see alot of post about other issues but the 1.5 cockpit experience was much better overall. Better sharpness on instruments and more natural lights and colors. I believe (hope) this will be fixed.

After FW update, is it necessary to default before calibration and press the Set button?

I am having this problem as well, one of the features that made me put 2.5 on the shelf for a while unfortunately. Playing without v-sync is not ideal for my setup, alot of tearing and unstable fps. Will hopefully be fixed.

Same here. Getting close to a 1.58 reinstall unfortunately. Want to enjoy my viggen :)

I have had them since the Gen 1 version. I think that it will outlast me at the very least. It is industrial materials throughout.

That is how the instruments are for me to on every AA setting, almost unreadable, very jagged.

A big revelation for me. Had massive screen tearing while looking around with trackir and randomly did the alt+enter trick. Tearing gone. Next get the instruments and cockpit as sharp as in 1.58, hopefully after an update soon.

Trying to figure out the settings to make 2.5 work for me. Any way to limit fps without using vsync? which removes 20fps at least. Without vsync i am getting between 50 to 70 fps and that makes it feel like i stutters especially with trackir movement, because of the inconsistency. In 1.5 i had vsync on and the fps was locked at 60 and it felt very natural and smooth. Thanks for any tips.

Yes i saw that while testing. A dream for me now would be to have the 1.58 cockpit with the deffered shading 2.5 map only. Would be a nice compromise and maby a few more fps. I thought the "old" cockpit was perfect. Time will tell i guess.

My problem right now is not getting playable fps but crazy amounts of tearing. If i activate vsync in game it caps the frames at 30-40ish fps and stutters alot. I get 60+ without vsync. The middle ground i found is using adaptive vsync in nvidia control. But still annoying tearing but not 20+ fps loss and stuttering...hmm to much give or take at the moment for me to be happy about the update. I5-4690, gtx1060 6gb. 16gb ram.

Thanks! What got me was that some did not have blue tint at all as seen, and those that had it was very bright blue.

First test on 2.5. Start from runway. Blood on heading ring? very blue gauges. Anyone getting the same?