-
Posts
200 -
Joined
-
Last visited
Content Type
Profiles
Forums
Events
Everything posted by Chapa
-
look at if your numlock and/or scrLock key are activated. I remember having issue with shortcut not working with my bluetooth surface keyboard because not always activated by default. or if the shortcuts are not bind to plane functionalities
-
Yes I use these shortcuts. In fact, it’s because they exist I stopped using OTT. I am playing only DCS so no need to manage multiple VR profiles
-
I use the game shortcuts to change the AWS mode on a daily basis. I even made voice attack commands for that and it works perfectly. I don't use Oculus Tray Tool or other launcher tools. Except enabling the ScrLk key on your keyboard to enable the Numpad, checking the app managing your keyboard if you use gamer keyboard and try a DCS repair, I don't see any reason why it doesn't work for you. Just to be sure, the shortcuts are done with the Right Control key
-
Nvidia’s first 2020 driver update also improves VR game quality
Chapa replied to Hellcat's topic in Virtual Reality
Nice to see some investment in VR but I ask myself why only Turing GPU ? I have the feeling that these kind of features like it is the case for ray tracing, will become the arguments to sell new generation of GPU because it becomes hard to improve performances without crazy Watts and GPU size requirements. Concerning the list of supported games, it’s look bullshit because customers are able to test their games by themself... Love the NVidia stuff but they give me the same bad feeling than a lot of GAFA that seems ti think that they always know better than their customers (i.e. the stupid forced update of our oculus, Apple bad design choices etc... :) -
DCS is not in the GeForce Experience list but it is in the list of Nvidia Control Panel/Nvidia inspector profile list: The profile name is : Digital Combat Simulator: Black Shark With some default settings applied and different than the global default profile
-
No, it has only effect in the Oculus app.
-
IPD settings in DCS should be called world scale. In summary, set your inter-pupillary distance in the Rift S app. In DCS, set the Force IPD settings the way the scale seems right for you. Stick size is generally a good way, pilot hand size when there is a pilot. To mesure your inter pupillary distance, there is an iOS app (probably android also) that works very well. The App name is EyeMeasure. 0.1 mm difference with the IPD mesured by optician for me Note that the IPD settings in DCS should be adjusted each time you fly a different plane
-
I found that: https://forums.eagle.ru/showthread.php?t=255963 It could be related. I don’t have this plane so can’t help you more. To compare things, build a mission and fly the same path with different planes to be sure and to be able to maybe isolate the issue.
-
You have a nice workaround so it’s ok but I think that the issue could be solved by some bios settings because it seems related to startup sequence. For example, it’s not rare that the PCIe x4 port bandwidth is shared with something else (SATA port or front panel usb port). Other idea is to verify in the device manager that the power management settings is not enabled at the PCIe USB ports level. Note that I find stupid that the oculus services are started by default at startup. I like your workaround that looks like s better design overall and avoid battery drain also
-
@Jopasaps Please don’t answer without knowing you have given new opportunity to Viper to express his frustration. Unsolvable bug... @moderator Close the thread ? :)
-
I am more curious to try if the same command but for 60Hz works. It would give 3/4 real frames and maybe less ghosting
-
[REPORTED] High-quality A-10C cockpit switch logic
Chapa replied to Redglyph's topic in Controller Questions and Bugs
The new cockpit is gorgeous! I agree about the lightning issue, it’s really annoying. I am starting the basic qualification campaign and even with lights on, I see nothing in VR, too dark. Concerning the view, I did a snapview and it seems to do the job for the moment. The issues will be solved, no need to worry and be so rude... -
I understand your workaround with the Hub turned on after... not a good idea even if it can work. Just don’t be surprised if you have stutters because the bandwidth sharing. Note that depending the motherboard and electronic quality, the issue can stay the same... Exemple with my Rog Strix z370 egaming: 1 controller is ASMEDIA, so it created stutter and was not able to handle the Rift alone. 1 controller for USB 2.0 so not able 1 controller USB 3.0 that could in theory handle it BUT... I discovered that the bandwidth was in fact shared with the bluetooth and because my keyboard is bluetooth, I had sometimes the issue.... Using other USB 2 keyboard, no more issue... Because I was not able to free the USB to keep the controller for the Rift, I bought a PCIe card. Hope your hub will solve your issue.
-
Your connection problem don’t come from Oculus but the way you have connected it. The Rifts S needs a dedicated USB 3.0 controller, the full bandwidth it provides. Your motherboard has probably 2 or 3 USB controllers. The USB 3.0 ports are linked to the controllers but there are always more than one USB port per controller, so the bandwidth is shared, so the issue... There are two ways to solve the issue: 1) you are able to free some USB ports to isolate one controller and plug your Rift on it. Your motherboard manual can give some hint. The device manager allows to display the devices list by connection and really see to which USB controller things are connected 2) Buying an external USB 3.1 gen1 PCIe card. It must have a dedicated alimentation (not directly from the PCIe port) and you must buy a card with controller not from ASMedia, so avoid all cards with USB 3.1 gen2 and USB-C port because the controller is most of the time ASMedia one. This one has solved the same issue for me: https://www.exsys.ch/de/pcie-karten/usb-3.0/standard/pcie-usb-3.0-karte-2-ports-renesas.html (if you go this way, there is a jumper on the card to move to give it power from you alimentation. According to your alim, it is possible that you will need a Molex to SATA adapter) For sure, VR is not really plug and play and requires good understanding about the settings and tuning depending your needs in DCS. But as you said, when tested difficult to come back on monitor
-
My opinion is that Virpil should consider a WarBRD throttle inspired from the current CM2 version and keep the CM2 name for a model keeping the strenght of the V2 model (with the lock button between the left/right throttles to avoid the software issue without it) Love my Virpil stuff anyway.
-
The thread you read was about blackshark 1. Blackshark 2 is compatible, I bought it last sales and use it with Rift S. Concerning your question, all plane are ok in VR. The Mig21 have issue if you look outside the cockpit (the outside of the plane is not modelized in VR) but the cockpit itself and module overall is awesome. As far as I know, all modules works in VR, I just miss three of them
-
FPS bump by disabling GameDVR in Windows 10 via registry
Chapa replied to Mustang's topic in Game Performance Bugs
From my test, the registry tweak has no impact at all. It even doesn’t change the fullscreen mode. But there is an impact with ALT+ENTER and it is visible in VR also with the Oculus HUD Render App Graph. For exemple, before alt enter, the FPS oscillate between 70 and 72.5. After alt enter, it is clearly more stable at 72.5 with drop at 70 clearly more spaced in time. UPDATE: With Rift S, pressing ALT+ENTER to have the mirroring view full screen improve the FPS, it can jump to the +2.5 FPS up range or simply stabilize. No registry and shortcut tweak required... Can avoid some AWS trigger so not so bad and cost nothing to press ALT TAB after launching DCS -
FPS bump by disabling GameDVR in Windows 10 via registry
Chapa replied to Mustang's topic in Game Performance Bugs
I tooks time to do serious testing by following some repeatable protocol to compare FPS. First, the context: Windows 10 Pro 64 bits 1909 (up to date) Nvidia driver 441.66 (up to date) DCS Open Beta (up to date) Monitor 5120x1440 DCS settings: High Quality Preset DCS Custom settings: - Civ. Traffic = OFF (to avoid some imprevisible event) - Full Screen checked NVidia Control Panel: As default, no custom settings NVidia Profile Inspector: As default, no custom settings All test are done here: Plane: TF-51 Map: Caucasus Instant Action: Cold Start in Krymsk Move/View: No move, Cockpit view exactly as the mission is loaded Measure time: After 10s and before 60s because at 66s there are some event that change the FPS, so mesures can't be done and would be irrelevant Goal: Impact on FPS only. Loading time, TrackIR smoothness are not measured at all Settings compared: 1) Game Mode ON/OFF 2) Checking the "Disable Fullscreen Optimization" for All Users checkbox for the DCS.exe & DCS_Updater.exe shortcuts 3) Applying the Registry Tweak proposed in the first post in this thread Summary of the results (Remember Windows 1909): 1) No gain in FPS to disabling Fullscreen Optimization from the shortcuts and/or applying the proposed Registry Tweak 2) The only way to see Excusive full screen in action is by checking "Disable Fullscreen Optimization" from the shortcut. The registry tweak alone don't do it... 3) There is a small gain in FPS by doing this steps: - Launch DCS but with another windows already open (Not Chrome!!! but an empty txt file for example) - Launch your mission - Press ALT+TAB to swtich App and go back to DCS - Press ALT+ENTER Here are the tests, actions and results, I have obtained: Test initialization: - Set DCS graphic settings as describe in the context part - Exit DCS - Drop the fxo and metashaders folders in Saved Games - Launch DCS and the TF51 mission - (DCS recompile all the shaders, long loading) - Exit DCS - Prepare settings for the first test - Restart the computer TEST 1: No Registry tweak | DCS shortcuts with checbox not checked | Game Mode OFF FPS at launch: 83/84 FPS after ALT+TAB: 82/83 FPS after ALT+ENTER: 84/85 => Improvment being in fullscreen and after ALT+ENTER ------------------------------------ - Change Game Mode to ON - Restart computer ------------------------------------ TEST 2: No Registry tweak | DCS shortcuts with checbox not checked | Game Mode ON FPS at launch: 83/84 FPS after ALT+TAB: 82/83 FPS after ALT+ENTER: 83/84 => Improvment being in fullscreen and after ALT+ENTER => With Game Mode ON, the FPS tends to be more often on the lower value (-0.5 FPS) ------------------------------------ - Change Game Mode back to OFF (seems a little bit better without) - Check "Disable Full Screen Optimization for all users" checkbox for DCS.exe & DCS_Updater.exe shortcuts - Restart computer ------------------------------------ TEST 3: No Registry tweak | DCS shortcuts with chekcbox checked | Game Mode OFF 84/85 - At launch 82/83 - After ALT+TAB 84/85 - After ALT + ENTER => After ALT+Enter, the FPS tends to be more often on the upper value (+0.5 FPS) ------------------------------------ - Tweak the Registry as proposed - Restart computer ------------------------------------ TEST 4: Registry tweak | DCS shortcuts with chekcbox checked | Game Mode OFF 83/84 - At launch 81/82 - After ALT+TAB 84/85 - After ALT + ENTER => No change with Registry Tweak => The exclusive fullscreen mode is enabled. There is a delay with black scren when pressing ALT+TAB ------------------------------------------------------------------------ - Uncheck shortcuts: Disable fullscreen optimization checkbox - Restart the computer ----------------------------------------------------------------------- TEST 5: Registry tweak | DCS shortcuts with chekcbox not checked | Game Mode OFF 83/84 - At launch 82/83 - After ALT+TAB 84/85 - After ALT + ENTER => The exclusive fullscreen mode isn't activated by having only the registy tweak in place Probably nothing new here because I remember someone saying that he observed small increase in FPS by the ALT+TAB & ALT+ENTER sequence. Personnaly, I will apply the registry tweak and shortuct settings because less software layer between the gpu and the game can only be better and I suspect that the real win could be related to tracking (VR, TrackIR): less layer => less latency Sorry for the long post but I did the job for me, so why not sharing it. -
FPS bump by disabling GameDVR in Windows 10 via registry
Chapa replied to Mustang's topic in Game Performance Bugs
Disabling Fullscreen optimization can be done without tweaking the registry. 1) Go to C:\Program Files\Eagle Dynamics\DCS World OpenBeta\bin 2) Right click on the DCS.exe file 3) Go to properties 4) Compatibility Tab 5) Click button: Change parameters for all users (I have french windows so the button could have different name) 6) Check Disable fullscreen optimization In DCS, check Fullscreen settings. ALT+Tab behaviour exit the fullscreen mode (if other window open before launching DCS). You have to press ALT+Enter to go back to exclusive fullscreen mode. These two links can interest you: https://community.amd.com/thread/226321 https://skymirrh.github.io/CompatibilityManager/ I try in VR but can't tell if it really improve performances (need to monitor with Oculus Huds) but it is not worse. I tend to think that it would be surprising that DCS can profit from the new Windows 10 fullscreen mode. So, if not worse, can only be better... -
FPS bump by disabling GameDVR in Windows 10 via registry
Chapa replied to Mustang's topic in Game Performance Bugs
Windows 10 1909 here but this key is missing: GameDVR_FSEBehaviour, however all other exist. Something has probably changed between 1903 and 1909. -
Interesting first feedback, thanks you. I read that hand tracking is available on Quest because it can use headroom from a Qualcom chip to do it without impacting FPS. However, it would not be possible with the Rift S because it don’t have this chip and no other way without impacting rendering. But I think as you, the Quest will become the flagship. The next iteration will just be better than both and keep the technologies initiated by the Quest
-
Bought the Buttkicker Gamer 2 Specifically for F-14 - love it
Chapa replied to flameoutme's topic in DCS: F-14A & B
@flameoutme: you kick my butt to push the trigger. Was not easy to find reseller in Europe with price not to far from the US prices but job done. Have to wait now :) -
There is probably a market with DCS but they should provide more serious youtube video. One of them being in a non clickable cockpit and the other one how to fly without a joystick are at least not well designed to appeal the people here and even the craziest beta testers :) Let me think that we are not really their target market but who know, maybe good news soon
-
You're welcome! I have the feeling that there are sometime bug that don't trigger new settings... (anistropic filter is sometimes capricious... and need restart... sometimes not) I took the habit now to quit/restart for every change and when I change textures settings, I also delete the fxo and metashaders2 subfolders in Saved Games\DCS folder. I lost too much time during tuning, thinking everything was ok to discover at the next startup that something was wrong again...