Arctic

I have the same issue with adding an alias for "Request Refuel". Tried it for "Bandit" and "join" as well, same issue. At first i thought it might be a problem with commands that have no alias yet but Bandit has 4 already... Havent tried to export, edit externally and import the commands yet, maybe thats a way...

Received #2269 today and just installed it. Works like a charme!:thumbup: Way better than the old slew Sensor, that was horrible! Buttons instead of axes would have been better before... My Warthog was bought in 2012 and the Throttle had Fw20, so i updated to 23. Great upgrade for the Warthog!:pilotfly:

I also downloaded Process Lasso now. I guess I'll just stick with that, since DCS is playable now. Thanks cabzi and everybody else!

I just checked that again all CPU Cores were selected for DCS (like before the reinstall). However, if i only select the last 5(10) Cores DCS is running without one processor at 100% all the time (more like 80-90 on one, and a bit on a few others...) , but much better. So, could be that this fixed it! Now i wonder if i really need third-party apps to do that automatically...

I also have microstutters in 2.5, even with low Graphic Settings and 120+FPS with that, every few seconds i get a small stutter. 1 CPU Core is at 100% while in Game all the time (All others are at 5-10%. Other people wrote that 2.5OB uses CPU much better (multiple Cores, and not 100% all the time the simulation is running...). I tried things that were suggested in other Threads like Power Settings, Hyperthreading on/off, updated Nvdidia Driver and checked the 3D- settings, updated my BIOS, then finally uninstalled 2.5 OB and redownloaded it again to only see that sadly nothing changed... CPU was clocked at 4 up to 4.4Ghz which also made no difference, 1 Core at 100% and stutters... And I haven't even tried VR yet... The new Version really looks amazing, but is unplayable... I dont have similar problems in any other Game/Application...

Since there is no Display in the F-5E (like MFCD, Shkval,...) Resolution of Cockpit Display setting is irrelevant for the F-5E and has nothing to do with the readability of labels in the F5-E cockpit. Pixel Density Setting in DCS itself is only working for Oculus Rift at the Moment but should do the trick if you are using the Rift, like tom said. Texture quality should also be on high, for sure. If you want a higher Pixel Density with the Vive: - Quit DCS and also SteamVR (it is not necessary to quit Steam). - Go to: ?:\Program Files (x86)\Steam\config\ - Make a Backup of the steamvr.vrsettings file ! - Open the steamvr.vrsettings file with Notepad or something similar and insert the following line somewhere under "steamvr" : { section "renderTargetMultiplier" : 1.5, So it should look like this, for example: You can change the value "1.5" to what your grahpics card is capable of. If this gives you much lower FPS, try 1.2 for example. It played a bit with this setting and saw that this setting wont effect FPS in the F5-E too much... Even on 0.5 it gave me no real FPS boost, but it is unplayable for sure because of the low resolution. But feel free to try 2.0 for example. DCS and steamVR must be closed to change the value every time. You should know that this settings changes not only DCS but also every other VR Game resolution. Have fun!

Hey, so, for the VR Problerm here is the Logs Folder (Last crash occured on 10:02PM MEST). It also happens without (!) any Weapons loaded. I was flying with the F5, set the "Guns, Missiles and Camera Switch" to upper position, External Stores Rotary Switch to RIPL and outer (A2A Switches) on the Armament Position Selector to up/on. When I press the Release Button, DCS will crash. The track file for the Afterburner Problem will be provided by zerO_crash. Thankyou !:pilotfly: Logs.rar

Hey BST, thanks for another great Module !:thumbup: Some Bugs we figured out until now: - Afterburner sometimes wont light up despite the fuel consumption gauge shows higher consumption - (apparently only in VR) while pressing Weapon Release Button (Rockets/Bombs) DCS will crash, not only for me but also for others VR users as well (both HTC Vive users, i dont know if it also happens with Rift) And now back to the Pit...!!!!:pilotfly::joystick::thumbup:

Well, it would be Awesome if it's true ! Got one week off, this would be the first time that my holidays fits a DCS release perfectly... :D

I recently upgraded my old CPU (I7 2600K @ ~4,4GHz) to an new 6 Core I7 6850K which is not overclocked yet. It gave me better FPS especially in VR, where its about every ms... Only for 4K, which i have since a year or so now (with a 980 Strix at the moment), my old CPU was good enough. For the standard User, IMO, there's no need to upgrade an CPU like the 2600k... Better spend the money on an 1080 for 4K And for Full HD a 980 or less is also enough for a decent experience in DCS...

While playing online, this only happens to me when people join special modules. It also happens without VR (Black Screen for like a second), but its worse in VR for sure.

So weit Ich weiss gibt es das bei der Mirage nicht.

Vorne links auf der unteren Konsole ist ein grauer Drehschalter, bei den Fuelpumps bzw neben dem Tankklappenhebel. Wenn die Tankklappe dann offen ist scheint ein Licht hoch am Boom entlang. @Hemmet: die Tankklappe kann auch im Cockpit mit der Maus bedient werden, das ist der oben beschriebene Hebel.

Yes, its called "smartresponse" located in the monitor settings. You can leave it turned off, fast, faster or fastest... But while the response time gets smaller, ghosting gets worse. ;)

When you get it, the first thing you should do is to set DisplayPort Mode to 1.2. Mine was set to the old standard with 30FPS- took me an hour to figure out why this was the case... :D