-
Posts
942 -
Joined
-
Last visited
Content Type
Profiles
Forums
Events
Everything posted by FoxTwo
-
Some CPU BIOS settings are pretty bad for DCS VR...
FoxTwo replied to RealDCSpilot's topic in Virtual Reality
It depends on the CPU. On the 10 and 11 series intels, MCE will take power/heat budget away from the single core boost in order to guarantee the higher overall multi core boost. On the 8 and 9 series it was a performance adder with no real downside. -
Some CPU BIOS settings are pretty bad for DCS VR...
FoxTwo replied to RealDCSpilot's topic in Virtual Reality
Multi core enhancement or Enhanced Turbo (MSI) sacrifices single core boost performance for higher overall multi core performance. It's not about power savings, it's the opposite. It's a form of factory overclocking but will only benefit applications that specifically utilize multiple cores, which DCS currently does not. -
For the G1 vs the G2? They were running at the same effective resolution, performance was identical.
-
I recently used my G1 again as my G2 cable had died. Dialing up the G1 (200% steam, 100% DCS) to the resolution I normally run my G2 at (100% steam 80% DCS) resulted in about the same overall image quality. I think the 6900XT is a good choice for DCS if you can get your hands on one.
-
The director lights are difficult to see in real life. Most pilots just fly formation.
-
[USER ERROR] UFC button bindings don't do anything
FoxTwo replied to FoxTwo's topic in Resolved Bugs
Apparently this was changed in one of the little fix patches after 2.7, because I completely redid the remaps for the MFD buttons (that don't work) when 2.7 came out. Validating against a repaired default.lua shows that the be the case. Now they essentially match what I did in my code, which is good. But how about doing the same thing for the MFD bindings so they work properly? Why are any icommandplane functions in the input lua at all? This isn't a circa 2013 FC3 aircraft. -
For seated/desk use, a single lighthouse should be sufficient. If you want room scale, you want to two or three depending on your room size.
-
By the time the 30 series can be reasonably had, it'll be time for the 40 series or RDNA 3.
-
Guess I'll fix this one myself too. For anyone who needs the bindings to work: {down = ufc_commands.Button_1, up = ufc_commands.Button_1, cockpit_device_id = devices.UFCCONTROL, value_down = 1.0, value_up = -1.0, name = _('UFC Button 1'), category = _('UFC')}, {down = ufc_commands.Button_2, up = ufc_commands.Button_2, cockpit_device_id = devices.UFCCONTROL, value_down = 1.0, value_up = -1.0, name = _('UFC Button 2/N'), category = _('UFC')}, {down = ufc_commands.Button_3, up = ufc_commands.Button_3, cockpit_device_id = devices.UFCCONTROL, value_down = 1.0, value_up = -1.0, name = _('UFC Button 3'), category = _('UFC')}, {down = ufc_commands.Button_4, up = ufc_commands.Button_4, cockpit_device_id = devices.UFCCONTROL, value_down = 1.0, value_up = -1.0, name = _('UFC Button 4/W'), category = _('UFC')}, {down = ufc_commands.Button_5, up = ufc_commands.Button_5, cockpit_device_id = devices.UFCCONTROL, value_down = 1.0, value_up = -1.0, name = _('UFC Button 5'), category = _('UFC')}, {down = ufc_commands.Button_6, up = ufc_commands.Button_6, cockpit_device_id = devices.UFCCONTROL, value_down = 1.0, value_up = -1.0, name = _('UFC Button 6/E'), category = _('UFC')}, {down = ufc_commands.Button_7, up = ufc_commands.Button_7, cockpit_device_id = devices.UFCCONTROL, value_down = 1.0, value_up = -1.0, name = _('UFC Button 7'), category = _('UFC')}, {down = ufc_commands.Button_8, up = ufc_commands.Button_8, cockpit_device_id = devices.UFCCONTROL, value_down = 1.0, value_up = -1.0, name = _('UFC Button 8/S'), category = _('UFC')}, {down = ufc_commands.Button_9, up = ufc_commands.Button_9, cockpit_device_id = devices.UFCCONTROL, value_down = 1.0, value_up = -1.0, name = _('UFC Button 9'), category = _('UFC')}, {down = ufc_commands.Button_0, up = ufc_commands.Button_0, cockpit_device_id = devices.UFCCONTROL, value_down = 1.0, value_up = -1.0, name = _('UFC Button 0'), category = _('UFC')}, {down = ufc_commands.Button_Dot, up = ufc_commands.Button_Dot, cockpit_device_id = devices.UFCCONTROL, value_down = 1.0, value_up = -1.0, name = _('UFC Button .'), category = _('UFC')}, {down = ufc_commands.Button_Dash, up = ufc_commands.Button_Dash, cockpit_device_id = devices.UFCCONTROL, value_down = 1.0, value_up = -1.0, name = _('UFC Button -'), category = _('UFC')}, {down = ufc_commands.Button_ENT, up = ufc_commands.Button_ENT, cockpit_device_id = devices.UFCCONTROL, value_down = 1.0, value_up = -1.0, name = _('UFC ENTER Data Button'), category = _('UFC')}, {down = ufc_commands.Button_CLR, up = ufc_commands.Button_CLR, cockpit_device_id = devices.UFCCONTROL, value_down = 1.0, value_up = -1.0, name = _('UFC Clear Entry Button'), category = _('UFC')}, {down = ufc_commands.Button_TMR, up = ufc_commands.Button_TMR, cockpit_device_id = devices.UFCCONTROL, value_down = 1.0, value_up = -1.0, name = _('UFC Timer Function Selector'), category = _('UFC')}, {down = ufc_commands.Button_ALT, up = ufc_commands.Button_ALT, cockpit_device_id = devices.UFCCONTROL, value_down = 1.0, value_up = -1.0, name = _('UFC Altitude Function Selector'), category = _('UFC')}, {down = ufc_commands.Button_IFF, up = ufc_commands.Button_IFF, cockpit_device_id = devices.UFCCONTROL, value_down = 1.0, value_up = -1.0, name = _('UFC IFF Function Selector'), category = _('UFC')}, {down = ufc_commands.Button_TCN, up = ufc_commands.Button_TCN, cockpit_device_id = devices.UFCCONTROL, value_down = 1.0, value_up = -1.0, name = _('UFC TACAN Function Selector'), category = _('UFC')}, {down = ufc_commands.Button_AWL, up = ufc_commands.Button_AWL, cockpit_device_id = devices.UFCCONTROL, value_down = 1.0, value_up = -1.0, name = _('UFC All Weather Landing Function Selector'), category = _('UFC')}, {down = ufc_commands.Button_ON_OFF, up = ufc_commands.Button_ON_OFF, cockpit_device_id = devices.UFCCONTROL, value_down = 1.0, value_up = -1.0, name = _('UFC Radalt/TACAN/AWL/IFF ON/OFF Toggle'), category = _('UFC')}, {down = ufc_commands.Button_EMCON, up = ufc_commands.Button_EMCON, cockpit_device_id = devices.UFCCONTROL, value_down = 1.0, value_up = -1.0, name = _('UFC EMCON ON/OFF Toggle'), category = _('UFC')}, {down = ufc_commands.Button_TOO, up = ufc_commands.Button_TOO, cockpit_device_id = devices.UFCCONTROL, value_down = 1.0, value_up = -1.0, name = _('UFC Target-Of-Opportunity Selector'), category = _('UFC')}, {down = ufc_commands.Button_WOF, up = ufc_commands.Button_WOF, cockpit_device_id = devices.UFCCONTROL, value_down = 1.0, value_up = -1.0, name = _('UFC Waypoint Overfly INS Update Selector'), category = _('UFC')}, {down = ufc_commands.Button_WPN, up = ufc_commands.Button_WPN, cockpit_device_id = devices.UFCCONTROL, value_down = 1.0, value_up = -1.0, name = _('UFC Weapons Function Selector'), category = _('UFC')}, {down = ufc_commands.Button_BCN, up = ufc_commands.Button_BCN, cockpit_device_id = devices.UFCCONTROL, value_down = 1.0, value_up = -1.0, name = _('UFC Radar Beacon Function Selector'), category = _('UFC')}, {down = ufc_commands.Button_IP, up = ufc_commands.Button_IP, cockpit_device_id = devices.UFCCONTROL, value_down = 1.0, value_up = -1.0, name = _('UFC I/P Button'), category = _('UFC')}, {down = ufc_commands.Button_SVE, up = ufc_commands.Button_SVE, cockpit_device_id = devices.UFCCONTROL, value_down = 1.0, value_up = -1.0, name = _('UFC Save Data Button'), category = _('UFC')},
-
You know it doesn't really work without the base stations right? And if you do want to do any other VR, you're going to need controllers. It's not a $799 complete VR experience, it's $1399 and right now, it's an unknown quantity since review units haven't really made it into anyone's hands. Personally I'm waiting. The G2 is fine for now, if the HTC is better that's great I may upgrade later on but so far it's not exactly blowing my skirt up.
-
Old bug, happens to every module. Maybe one day...
-
There are friction pads inside the throttle, they will wear down particularly if you have it cranked to the max. Contact TM support to get replacements.
-
Not that I'm aware of.
-
You can fix this yourself, right now if you don't want to wait for the ED patch to go out. Edit: \Program Files\Eagle Dynamics\DCS World OpenBeta\Mods\aircraft\MIG-21bis\Cockpit\Systems\R_NAV_data_Syria.lua At line 76, the problem is an unescaped ' character Change this airbase = 'Tha'lah', -- 8 to this airbase = 'Tha\'lah', -- 8
-
So I'm not sure if this is related to the mouse not being bound to the window or not but DCS is creating two separate "box_mouse_cursor" settings in the options.lua One is under [VR] and the other is under [graphics]. Tested with a completely default options file newly generated by a clean DCS launch. options = { ["VR"] = { ["box_mouse_cursor"] = true, }, ... ["graphics"] = { ["box_mouse_cursor"] = false, }, } @BIGNEWY Thoughts?
-
150% steam resolution AND msaa 4x? Uh... yeah. Try 100% steam resolution, 80% DCS resolution and msaa 2x. Unless you've got a 6090 in that PC.
-
It's still not what I'd call good. 2.5.6 really globally broke in cockpit instrument/panel back lighting and I guess the MI-8 is just too old of a module for them to give it much attention.
-
You can just click on the play button in WMR to disable mirroring. Note that mirroring has no effect on performance.
-
I don't understand why these elements do their best to crash SteamVR and bring the frame rate into the Seconds Per Frame territory, but if you could like... make that not happen that would be ideal. I don't know how you're compositing these elements onto the screen but whatever method it is, it absolutely destroys the frame rate in VR. Fix please?
-
https://www.digitalcombatsimulator.com/en/news/changelog/openbeta/2.7.0.5118/ Known Issues MiG-21 crash on the Syria map.
-
Wings folded = NWS high is 'sticky'. Wings unfolded = NWS is a toggle.
-
There's a visual distortion where the two halves of the canopy model meet. Wasn't super noticeable before but with the clouds, and in VR, it's pretty obvious.
-
This isn't star citizen.