ShuRugal

well, what a happy coincidence: I've just fixed the right toe-brake in my pedals so it works again. Now i have something to use it with.

keep getting "unable to activate" error. log attached.

Amusingly enough, it runs other VR apps just fine. I can put Elite up to 1.5 pixel density with no slowdown, using the same settings that had my mobile 780 stuttering at 1.0 density. No joy increasing graphics options in DCS, though. Oh well. Guess I'll be ordering a 1080 with my next paycheck. Actually... 1070. Passmark scores the 1080 at 11,900, and the 1070 at 10,900, but the 1070 is half the cost. Half the cost for less than a 10% difference in performance? hell yes.

Well, after more testing, it looks like if I use low presets, disable AA and terrain shadows, and set pixel density to 1.5, I can hold 45 FPS in Nevada... as long as Vegas is not in sight. In vegas i get 15 fps no matter what i do.

UPDATE: When launching with DCS2, I get into the main menu fine, but when i try to get into a mission, i get black screened to death. UPDATE2: solved the above, but it's even more of a slideshow in Nevada. Gonna be sad if i have to buy a new new graphics card...

yeah, i'm starting to think i may have goofed with the 1050, been near to a decade since i was in the market for a desktop graphics card. Still, i'll see what i can squeeze out of it.

6 was typo, 16 GB installed. GPU may not spec near as high as a 1080, but it blows the pants off my mobile 780, and DCS is the only application in which i have not seen significant gains so far. Will try 2.0 this afternoon and report back if that made a difference.

haven't tried it on Nevada yet. New rig is as follows: I7-6700K MSI GTX 1050 TI 4GT OC 6GB DDR4 Win10

can confirm. have performed a couple forced autorotations after dual engine failure from ice at altitude.

So, I have finally made the move from gaming laptop to gaming desktop... And the performance improvement in DCS is non-existent. All of the components in my new desktop spec 2-3 times the benchmark scores of my laptop, yet my Oculus framerate (using identical settings) has not changed at all. Other applications, however, have improved dramatically. I have also heard reports from other players with even better systems (SLI 1080s, as opposed to my singular 1050ti) that they also have an extremely hard time finding a balance of quality and framerate when using Oculus. What gives? I thought we solved the "DCS sucks at framerates" problem with the migration to DX11?

what, exactly, is all the fuss about the DCS P-51 about? Isn't the one in game supposed to be modeled off the one owned by TFC? Didn't they use flight data from TFC's 'Stang to develop the flight model?

If you want to fly on MIL power, you need to keep your speed above 300mph, otherwise the radiators don't get enough air.

throwing in my +1 as well; I know of two instances where I have TK'd on a confirmed hostile RAEO lock, both times with 27R. It should be impossible for me to make such a teamkill, because I never shoot in manual override.

you can always put a piece of scotch tape on your monitor and dot it with a sharpie.

sounds like the autostart script is flipping the engine selector switch before the engine-start cycle is complete for the #1 engine. If you flip that switch while the start valve is open (indicated by the light beside the startup switch), then the bleed air will switch over to the other engine. If your timing is perfect, you can use this to shave ~10-15 seconds off your startup by flipping over when the first engine passes 50~55%. However, the helicopter's engine-control unit does not know you've done this, so it does not restart the timer on the engine startup sequence when you select the new engine. TL;DR version: ECU runs starter for a fixed length of time (~30 seconds IIRC). If you switch engines during this time, it does not reset the timer, so the starter could shut off before the engine passes the self-sustaining point.

protip: the vertical bar beside the elevation number on your HUD represents the radar's vertical FoV, and the two dashes sticking out towards it represent your HUD FoV. If you want to find where a target you are scanning actually is in the sky: 1. maneuver the aircraft until the contact is centered in front of your AC on the HDD, 2. pitch up or down until the two dashes are bracketing the radar scan altitude bar. 3. target is now framed by your HUD. you can also reverse this process to point the radar at a portion of the sky you specifically wish to scan: put the HUD around it, raise or lower the antenna to line the bar up to the dashes, you are now scanning your target.

eh, the ABRIS doesn't have MGRS? (fairly certain, why would a Russian moving-map have a US-Military grid coordinate system?)

update: fixed it by running repair. no idea what that changed, but it works again now.

thank you, I am aware of that and, in fact, already use JSGME to manage my changes. I would hardly have created a thread about this if i had gone into the folder and found that the file was in stock condition.

So, this update seems to have broken my recent progress in creating custom toggle switches (specifically for the KA-50) I have attached a copy of my KA-50 default.lua, the custom entries were working until I updated. default.lua

New problem: UR control panel does not recognize button presses on my X55 stick. Throttle quad is recognized.

It is worth noting that this is only true if you are in a stable and stationary hover. There is a long-standing bug in the Shkval simulation in DCS that causes the range calculation to become wildly inaccurate if the shkval is slewed vertically (either by pilot command or by motion of the helicopter) while moving forwards. That aside, I have to say that I have never once burned out the laser in my shkval when I let the automatics do their work. The built-in cooldown timer after each shot is more than adequate to go through all 12 vikhrs in continuous fire, after which the time it takes you to RTB, rearm, and return to the fight should be sufficient to allow the laser to fully cool. Even adding in the rare cases where i go through all my vikhrs, rockets, and both belts of 30mm, I have never burned out the laser while using the automatics. The only way I can think of an exception to this (aside from cheating with infinite ammo or carrying 24 vikhrs) would be if you were fighting within just a few km of your FARP/airbase. In this case, however, it would be unrealistic in the extreme: If you have enough enemies that you need multiple full reloads to kill them all, they will overrun your position fighting at such close range. If you were directly defending you FARP, you would use a secondary FARP as your re-arm point to avoid being captured while on the ground.

update: By completely uninstalling and reinstalling all UR components, the issue was resolved.

From DCS.Log: 00098.519 ALERT EDCORE: Can't execute Lua file D:\Users\ShuRugal\Saved Games\DCS\Scripts\Export.lua - can't open 'D:\Users\ShuRugal\Saved Games\DCS\ScriptsTacnoworld_UR_DCSW.luac'