Jump to content

Fisherman82

Members
  • Posts

    699
  • Joined

  • Last visited

Everything posted by Fisherman82

  1. No I removed all mods and did a repair on DCS but that did not help. That image is not from a mod, its from DCS itself. You may see it flash by when you are flipping pages, its like a loading screen between pages. But in my case the maps never load in Nevada and Persian Gulf, only in Caucassus. And only in VR, it works if I stop the Oculus service and use the monitor instead. Skickat från min D5503 via Tapatalk
  2. When Im flying into the sun it is blinding me as it should, but it is also shining in through the front of the aircraft at the feet of my pilot.
  3. Thank you Then its just me then, I have no idéa what is going on Skickat från min D5503 via Tapatalk
  4. No one that can tell me if their kneeboard maps work in VR for Nevada and Persian Gulf?
  5. Noticed now that Persian Gulf dont work either. Only Caucassus work. I have a Rift S. Skickat från min D5503 via Tapatalk
  6. Has anyone else noticed that the Nevada kneeboard maps dont work in VR but they do when you use a monitor? The maps on the kneeboard for the Caucasus work.
  7. That seems to be the same situation that I have with my GTX 1080, and those cards are pretty close in performance as far as I know. Wonder what PD it would be possible to squeeze out with a 2080 super, if it would be worth the cost. Skickat från min D5503 via Tapatalk
  8. I used the IC pass version for 2.5.5 from the video for 2.5.5 from that guy but it still affect the graphics in old missions Skickat från min D5503 via Tapatalk
  9. It would be interesting to know what pixel density some of you others are able to squeeze out of your graphics cards and what cards you use and if you are using MSAA. Im on 2.5.5 so what you could run in that is most interesting. Skickat från min D5503 via Tapatalk
  10. Is it possible to use this mod only with the circular mask? Perhaps of only that is used it would not affect the graphics in old missions? Skickat från min D5503 via Tapatalk
  11. Yes Skickat från min D5503 via Tapatalk
  12. Hello, I used the VR shaders to great sucess, however I noticed that missions I created before in Nevada dont work, the colors are totally wrong, its unplayable. Does anyone know what is causing this? Is there something in the miz-file that can be changed? Skickat från min D5503 via Tapatalk
  13. I am using the ASW to 45 in the Oculus Tray Tool so my max is 40. I tried the rivatuner as SebastianR wrote and that actually worked, however the result was not so good. After a couple of days of testing different settings I have settled on running it at the following settings: MSAA x2 (cant be without it because it looks horrible) Pixel density 1.2 Anisotropic filtering 16x shadows medium, terrain shadows flat, global cockpit illumination off visibility range medium, trees 75%, water medium, preload radius max. When testing this it I take the Viggen at a morning mission and fly it max afterburner through the canyons as low as possible and look out to the sides. At PD 1.2 and these settings it is mostly steady 40fps, just very rare drops with some small stuttering. If I could I would like to use PD 1.3, I think the difference in clarity is pretty big between 1.2 and 1.3, its feels better for the focus of my eyes. With 1.3 i get more stutter when looking out the sides though, but actually not so much more than if I try PD 1.4. The wierd thing is that It does not happen every time I look out the side, it seems pretty random, even if I turn mirrors of. I cant pinpoint what is causing it, if its simply to high PD but when flying higher I have no problems at all, its constant 40 fps. I have a i5 9600K, MSI GTX 1080 8GB and 32GB RAM. DCS on SSD. What settings should I be able to run the Rift S do you think? Is PD 1.2 the limit or is there some setting in Nvidea that I could change to avoid the stuttering when looking at the fast moving threes so I should be able to cram out PD 1.3? Im running the stable version 2.5.5.
  14. No I cant because the problem is not in DCS, its in Windows, in scrollable things like the project list where you pick what screen to use. There it scrolls to the bottom. I desoldered the pots, but I still had a input, after some Google i soldered one resistor from the point for the center pin to each of the other points because then I have the same resistance between the center and to either side and that should give no signal according to what I read. And on the old Windows 7 computer I used for testing the inputs stopped and the z axis remained at 50%. However when I connected it to my Windows 10 computer for DCS it still says its got input. After some more Google I think its a universal thing with Windows 10 and Xbox controllers, I would need a driver for a Xbox controller that has not one z axis for the triggers that sits at 50% in neutral position but instead one with one Z and one RZ rotation axis so that 0% is the neutral position. I have seen screenshots of that in the Windows controller settings but I cant find any such driver. Skickat från min D5503 via Tapatalk
  15. If I would desolder the pot and bridge the right two points where the pots pins where (it had 3) could I then make it send absolutly zero signal? Skickat från min D5503 via Tapatalk
  16. So when I click on the taskbar to change audio output the list scrolls rapidly to the bottom, if I try to scroll up its fighting me to scroll back down so I can only pick the last thing on the list. Skickat från min D5503 via Tapatalk
  17. No, the trigger axis always has a microscopic input on it, its so little that it is not visible if I look at the controller settings in Windows for the axis. But in JoyToKey it is marked as if someone always is pressing the trigger Skickat från min D5503 via Tapatalk
  18. Hello, I need some help from someone who knows electronics better than me. I have built a buttonbox from a Xbox controller to be able to use the Oculus button without using the handcontroller since the Xbox button can be used for this. I opened the Xbox controller and soldered in some wires on the buttons I wanted to use in the buttonbox and got that to work exactly as I had planned. However the only problem is that I get a undesired input on button 13 in JoyToKey, that is the left analog trigger. The input is there despite that I see in the Windows controller settings that the Z axis has no input. I have not done anything with the left analog trigger. What input would it send if I would desolder the pots for both analog triggers? This does not affect DCS but is a pain in the *** in Windows since when I want to change screen or speakers it scrolls to the bottom of the list by it self so fast and stays there so I cant do anything. Is there a way to turn navigation with Xbox controller off in Windows 10 to prevent this? Skickat från min D5503 via Tapatalk
  19. Dont know because I dont have it anymore.. Skickat från min D5503 via Tapatalk
  20. Hello For years I used Target version 1.something until I one day thought that perhaps it was a new version out. Turned out to be 3.something so I was pretty much behind. However, since updating sometimes when I run a script and go into DCS I discover that my stick is not taking any inputs eventhough Trustmaster Combined is detected, only the throttle works. If I shut down DCS and the script and check in device manager it is unresponsive there as well. I might have to restart the computer to get it back. It does not always happen though. Has anyone experienced the same? Skickat från min D5503 via Tapatalk
  21. Yes I did it for DCS only, not globaly Skickat från min D5503 via Tapatalk
  22. Hello, I have got a Rift S and wonder if its possible to limit the FPS to 30. I have tried in the Nvidia Control Panel but it still tries to reach 40. I dont think I would mind going down to 30, at least I would like to try. What I dont like is when it fluctuates from 40 to 37 and 35 and so on. That causes stutter. It never goes below 30 with the settings I have now. Skickat från min D5503 via Tapatalk
  23. That is sad news indeed :( Skickat från min D5503 via Tapatalk
  24. I have been waiting for quite long now for the offset function from a waypoint to be implemented, specialy in VR I have no chance of remembering the coordinates given by a JTAC but I think I could remember "ADDER 215 for 10" for example. So I am quite supprised that this particular function has not been implemented yet since its essential for CAS in VR atleast and the Harrier had it from day one. It would be a game changer for CAS to me atleast. And that leads me to thinking that that function is not implemented in the real aircraft? Skickat från min D5503 via Tapatalk
×
×
  • Create New...