

Frusheen
Members-
Posts
791 -
Joined
-
Last visited
Content Type
Profiles
Forums
Events
Everything posted by Frusheen
-
DK2 order numbers were not sequential. These probably aren't either. I remember DK1 was and there was war when some countries got theirs ahead of others even when they ordered later and had higher order numbers. Oculus learnt their lesson.
-
Derek I don't think it's a good idea to quote your order number! EDIT: I saw nothing Derek.
-
Cyber has said on oculus forums those charges will disappear after a few days. It's just a card check. Unfortunately due to all the page refreshes I ended up with so many my credit card company locked my card lol
-
My god Icarus you are all over the place. Yesterday you weren't buying a Vive or Rift because of screen door. Today you want the Vive because you'll be able to see your switches. Surely you realize what you want is AR and not VR at all. Yet you post everything and anything VR related that you find on the Internet in the Vive and rift threads. Maybe you don't know what you want :music_whistling:
-
My card company locked my card due to the amount of $1 charges as the page kept failing and I resubmit so many times. I never received an order confirmation email but did get a order number on screen. Emailed support. I hope I don't loose my place in the queue.
-
The difference in price was evident with the two dev kits as well. It was to cover import duties. Are people sure that taxes aren't included in the euro price?
-
They will both have screen door so I guess you'll have to wait for cv2.
-
Any update on this issue?
-
I presume that includes all the backers who swore they wouldn't buy the rift after the takeover because Palmer had 'sold out' to Facebook. It'll be interesting to see how many of them turn down the offer of a free rift now:music_whistling: Oculus have just beaten HTC in the PR battle at least.
-
I'm thinking it'll be a touch under $400. But after buying dk1 then dk2 and waiting years for this release I'll probably pay more if I have too.
-
75FPS over Vegas strip I received my new GTX 980Ti today and spent the past few hours overclocking. Result- I manage 75fps solid over Vegas for the first time. I flew the huey from Nellis down the strip and landed by the Mi8 at McCarran. It was silky smooth. I got the core clock on the card up to 1.5Ghz and the memory to 7600mHz. My cpu is a 4770k at 4.2GHz. All settings are at minimum for now but finally having zero judder makes up for the lack of eye candy. No idea how it will fair when CV1 arrives but I couldn't keep using my 780OC and playing the waiting game for Pascal. I'll spend some time playing with settings to see if anything can be turned up.
-
small precise small joystick?
Frusheen replied to Elwood's topic in PC Hardware and Related Software
Chproducts still make small joysticks. They are expensive and more geared towards industrial applications. -
Thanks for the update spinter. I hope a fix for this is available soon.
-
That's a lot of new features. Great work Andrey and f410. I hope my Jetseat arrives soon!
-
Not working in 1.5 unfortunately. :cry: Please try to update this if possible. I'd love to get it working
-
Could you possibly post a basic mission that uses this script? I am very inexperienced with lua and the mission editor and I can't work out how to implement the script. I have added the sound folder to my .miz file using 7zip. I need to see an example I can open in the mission editor for the rest if possible. I would really like this feature for the oculus rift as the sling camera is useless in VR. Thanks! Fergus EDIT: Disregard! I just noticed the mission in the zip file.
-
Elite dangerous offers no output unless you use memory hooks (which often change with updates) so it's not even worth looking at Andrey.
-
I'm sure an x-acto blade will solve it. It's only a foam liner. Trackball and clickable cockpits works fine for me. I'm only flying helicopters so I don't need the keyboard. I use Viacom for the radios.
-
Nice report. Thanks for the link. "There was no light leak and the old trick of peaking through the nose hole at your keyboard will no longer be possible, the headset sits flush on your face and the only thing you will see is the virtual world." Hsb you might want to rethink all those switches!
-
Thanks Wrench. I'll take a look.
-
I remember having a mission a while back in 1.2 where voice commands were given for positioning over cargo. I tried the mission in 1.5 but it wouldn't work. I no longer have 1.2 installed. Can anyone tell me if this was a mod or a part of a mission script? I use the oculus rift so the cargo camera is of no use. I manage ok without it but the commands added to immersion when working with sling loads. I've tried searching but have had no luck. Can anyone point me to an example where this works in 1.5 so I could add it to my cargo missions. Thanks.
-
VAICOM 2.0 for VoiceAttack
Frusheen replied to Hollywood_315's topic in PC Hardware and Related Software
I just got this setup and working in 1.5 with my oculus rift DK2. Sling loads in the Huey are now so much easier. Thanks so much for the hard work and continued updates. This is a fantastic mod. -
I agree there is a lot of optimization needed with EDGE which is a higher priority. I mention gameworksVR and liquidVR so people might understand that traditional Sli is NOT what we want for DCS. Far too many people mention they'll buy a second graphics card and go sli thinking it'll help improve performance in VR. It won't! I do think that these APIs need to be factored now though so revisions to edge won't make it more difficult to implement them in the future.
-
Traditional Sli is not what's needed for VR. In fact it increases latency. We need VRsli which is a different animal. It's part of a set of APIs that form gameworksVR (liquidVR for AMD). It must be implemented by ED themselves.
-
I don't see a need to post in any VR threads anymore lol. Everything I write is a carbon copy of what Vicx says. He is absolutely right in this post and his others. Spotting targets in VR will undoubtedly be an issue. CV1 of rift or vive likely won't solve that. It would take over 8k per eye to come close to human vision and that is essentially what we are talking about. Acquiring targets with the old mark one eyeball in VR is years off. It will take compromises to make it work. Similar to those being implemented already to increase the number of pixels rendering far off targets. The other benefits that VR brings far outweighs the targeting issue for me.