

Thick8
Members-
Posts
905 -
Joined
-
Last visited
Content Type
Profiles
Forums
Events
Everything posted by Thick8
-
In 2.2.0 the landing light is on and I can see it is on with an F2 view yet there is no light projected on the ground from inside the cockpit. Ideas? edit: In VR in the A-10C
-
how is everyone dealing with clickable cockpit in VR?
Thick8 replied to hannibal's topic in Virtual Reality
Mouse camera 2017, webcam (mounted in front of throttle, facing the throttle), autohotkey, pink page turning fingerlette (on left index finger), trim buttons on the stick ( till I finish my finger mouse). It’s basically TrackIR for your finger. -
Newest update fixed it. There was apparently something wrong with the Openvr.dll file. Weird the clean and repair didn’t fix it.
-
Something else I just noticed is that I have no landing or taxi light.
-
Really enjoy setting my radios and calling out ATC, tankers, AWAC by name. JTAC is messing me up a little bit but I’ll keep practicing. The fact that the system uses keywords is very cool so I don’t have to follow an exact phrase for the system to recognize a command. The system seems to have a problem recognizing me saying Vaziani. It kept sending the command to Sogalund. But I have easy radio turned off so... Then I switched to 139.00 to call Sogalund and my pilot voice said “ Vaziani, inbound”. WTF! LOL. I need to read the commands list to Cortana a couple of times I think.
-
Got it working. For some reason VA wasn’t registering the joystick button presses via autohotkey. I reinstalled VA and it started working.
-
Hmm. Can't seem to get it working. Installed VA, VIACOM, and Whartsell's static ATC. Using the # pad buttons 1, 2, and 3 will bring up the Transmit dialog in VA. The command is recognized, yet it does nothing in DCS. Any ideas? Have tried several commands. Using the latest DCS 1.5. Tried in both VR and monitor
-
Anyone?
-
Heck, me and Cortana are BFFs. She even knows all my bad accents.
-
Both have been around for a little while now. Which has the most complete A-10c voice command profile? Don't feel like fiddling at all. I just want to issue the commands in a natural voice using the DCS commands. Like "Two, attack air defenses at my spi with missiles from the north". I won't need to manipulate cockpit switches with it.
-
Understanding Pixel Density - Making sense of it
Thick8 replied to DerekSpeare's topic in Virtual Reality
They are already up scaling from a lower resolution. 1440p I think. Don’t know how this will look upscaled maybe it will have an added benefit of some sort of internal color averaging that may resemble FSAA. Who knows, their website is full of impossible unachievable promises. -
Thanks but that didn't fix it. Any time anything gets blown up. Whether it's done by me or my wingman. Doesn't have to be on the screen. I loosed a mav, turn 180 degree and when it hit, CTD. My wingman took a SAM up the tailpipe within my sight, CTD. What is different about an explosion that could cause this? I even took the overclock off my CPU and GPU to see if that might have an effect on it.
-
Rolled back the Nvidia drivers to eliminate a frequent game freeze. That is fixed. I also uninstalled and re-installed DCS2.0 in an attempt to fix the issue. Now any time I blow something up or something blows me up I get a CTD. This is happening after the DCS reinstall with 3 different Nvidia drivers. It doesn’t matter what graphics setting are. From low to high and 1 to 1.5 supersample. This is starting to piss me off.
-
I used a 22” touch screen monitor with Helios until I went VR last week. Simple setup and all of your buttons and dials can be accessed right there. This also allows you to adjust you main monitor so you are looking outside the aircraft instead of half the screen being taken up by the dashboard (MIP).
-
Found the answer in another thread. Nvidia driver issue.
-
New Nvidia drivers update = warps, stutters and freezes on CV1?
Thick8 replied to Buckeye's topic in Virtual Reality
Yep, me too. Thanks for figuring this out. I didn’t realize that the creators update turned auto update back on. Rolled back the drivers and In a 30 minute, heavy UI quick mission it only did it twice. never does it at all on a monitor so I’m not sure if this is normal. Is it? It is still crashing to desktop when my plane is destroyed. I’m thinking this is not normal. Ideas? -
I guess it could be. In addition to the aforementioned issues; when I crash the plane, DCS crashes to desktop. Didn't do this until today after the reinstall. SteamVR has updated twice for me this evening. Maybe I should opt out of the beta. I don't know why I thought this was going to be painless. Hardware upgrades never are...
-
This was not an issue the other day as far a I can recall. The display will go to the Steam holodeck with with the waiting animation (3 pulsing bars on a blue background) for a few seconds every once in a while. The game freezes for that period of time, and then resumes where it left off. It does this regardless of the level of detail chosen. It seems to have gotten worse as it happens frequently now. Like for 3 to 5 seconds every 10 to 15 seconds. I did a complete reinstall of DCS 2.0 and the Nvidia drivers just to be sure it didn't have anything to do with my previous Helios install. Any ideas?
-
Samsung Odyssey review by someone who’s never played VR
Thick8 replied to Speedywrx's topic in Virtual Reality
Post moved to own thread -
Where is the tracking coming from? My mouse glove is almost done. Just stripped down a wireless mouse and tracking it with an old webcam. 2 buttons and scroll input should do.
-
l played a single player track after a mission and it recorded all of my head movements and actions. I would just like to be able to turn this feature off. Don’t know why this should be so hard or such a big deal to implement.
-
Is this that hard to do? I would like to see if there is a performance gain in VR.
-
I just have to say that it is such a pleasure to be able to come to the DCS forum and have thoughtful, polite, and intelligent discussions. Sometimes it seems that this is the last bastion of civility.
-
What he said. If I were to guess; I think that the 2K per eye OLED is next up to bat, while maintaining or slightly increasing FOV. Then the focus (pun intended) will be on lens development for a while before FOV and PPD see a significant rise. The big players are in this for the long haul so I wouldn’t expect them to jump product cycle theory. Pimax is the outlier here but they really don’t have a dog in this hunt yet. The 4K was a flop and they have stated that they need more money to bring the 8K to market. I have seen dozens of promised start up VR products silently disappear with investor money over the last 2 decades the I am not very optimistic about Pimax.
-
It made sense for me as I passed on the rift and vive. I intend to upgrade when the tech gets better. I am hopeful for the Pimax but will probably wait for one of the big players to come out with a significant upgrade.