@Hornet...I agree about positional tracking ..although it will be useful in a cockpit when the resolution is bumped up in CV1. .............. To Get Riftup working with Vorpx.......you can download this free hex editor http://www.mh-nexus.de ...Open the editor then click on file and then open...navigate to your ovrservice folder ...for me it is C:\Program Files (x86)\Oculus\Service . Open the exe ....now do a search with the find option ...search for DKHD2. Take note of where it is. Then Search for DK2 ..copy the hex value for DK2. Then replace the hex value for DKHD2 with the DK2 hex value and add four zero's after it. Hex value for DKHD2 is 44 4B 48 44 32 For the DK2 its... 44 4B 32 . The new value should be 44 4B 32 00 00 . Enjoy Vorpx !!!

Last edited by willibeu on Fri Sep 19, 2014 11:32 am, edited 2 times in total.

@Hornet...I agree about positional tracking ..although it will be useful in a cockpit when the resolution is bumped up in CV1. .............. To Get Riftup working with Vorpx.......you can download this free hex editor http://www.mh-nexus.de ...Open the editor then click on file and then open...navigate to your ovrservice folder ...for me it is C:\Program Files (x86)\Oculus\Service . Open the exe ....now do a search with the find option ...search for DK2HD. Take note of where it is. Then Search for DK2 ..copy the hex value for DK2. Then replace the hex value for DK2HD with the DK2 hex value and add four zero's after it. Hex value for DK2HD is 44 4B 48 44 32 For the DK2 its... 44 4B 32 . The new value should be 44 4B 32 00 00 . Enjoy Vorpx !!!

Thanks for this, Willibeu. I think I understand. I am not home tonight but will try it when I get there. I run my RiftUP on a second computer where I have a second Vorpx install and would like it to work. I appreciate your advice.

Hi guys, please it is complicated to work RiftUp with new 0.4.1 runtime ? Yesterday (night I tested finally DK2 with new PC with 780Ti and after short test with upgraded First Law I have to say WOW! It is really good, smoth movement, accetable FOV, positional tracking good working, really good. Now I want to test with it RiftUp, what tweeking is needed for it to work with 0.4.1 Thx

Extract the attached executable, drag and drop the OVRService onto it, it will create a patched version with a .ritfup extension. Replace the current one in your Oculus/Servicefolder with the patched one (rename the existing one and remove the .riftup extension from the patched one), and run it.

If, when you open the Config Utility it now shows a DK2 instead of a DKHD2 prototype, then it worked and you should find you can now run VorpX.

You do not have the required permissions to view the files attached to this post.

Just tried Skyrim with Vorpx and ........Incredible!!!!!!. No settings in Vorpx needed adjustment. You can just hang by the river and look up at the mountains without playing at all. The scale is perfect and the 3D pops. Very Very impressed. Two things I did have to do though was turn off chromatic aberration fixer in vorpx controls. Us Riftups don't need it. ....and if you have shadow flickering...... in the skyrim prefs ini. change bDeferredShadows=1 to bDeferredShadows=0 ...for some reason it has fixed the shadow problem either way if its zero make it 1 ...if its 1 make it zero. People complaining about Vorpx costing 40 dollars are insane. Skyrim alone is worth the forty dollars.

Extract the attached executable, drag and drop the OVRService onto it, it will create a patched version with a .ritfup extension. Replace the current one in your Oculus/Servicefolder with the patched one (rename the existing one and remove the .riftup extension from the patched one), and run it.

If, when you open the Config Utility it now shows a DK2 instead of a DKHD2 prototype, then it worked and you should find you can now run VorpX.

EDIT: No luck - I contacted the seller, and apparently there is no stock...

Seems a couple of sellers do have stock, however - one is quoting US$656/pc (excluding shipping), and the other is asking for US$780/pc (plus US$40 shipping). Given that one can buy a Nexus 7 (with its 1200x1920 screen) for less than US$300, these prices seem unreasonably high. On the other hand, a 7" landscape 1920x1080 LVDS IPS panel is appealing...

EDIT: No luck - I contacted the seller, and apparently there is no stock...

Seems a couple of sellers do have stock, however - one is quoting US$656/pc (excluding shipping), and the other is asking for US$780/pc (plus US$40 shipping). Given that one can buy a Nexus 7 (with its 1200x1920 screen) for less than US$300, these prices seem unreasonably high. On the other hand, a 7" landscape 1920x1080 LVDS IPS panel is appealing...

Even if you get the display, the internal boards are not suppose to handle 1080p display, regadless if the signal is lvds. BTW, those display's are very heavy.

EDIT: No luck - I contacted the seller, and apparently there is no stock...

Seems a couple of sellers do have stock, however - one is quoting US$656/pc (excluding shipping), and the other is asking for US$780/pc (plus US$40 shipping). Given that one can buy a Nexus 7 (with its 1200x1920 screen) for less than US$300, these prices seem unreasonably high. On the other hand, a 7" landscape 1920x1080 LVDS IPS panel is appealing...

Hi Quppa,

I'm interested to buy this display, did you have/find a driver board for it? If yes please tell me where can I buy one?

VR Union MTBS3D Community Fund for Open-Source VR - VUMCOTo appreciate these honorable efforts, from now on, 5 dollars from every RiftUp sale will be added towards VR Union MTBS3D Community Fund.Those money will be given to community members supporting software efforts to integrate RiftUp or make VR software more open-source in general.

Community Fund VotingThe goal is to compensate community members for their valuable time spent on development.We'll setup a voting thread here every 30 days for you to allocate those funds. (Hopefully there will be something to allocate.)

RiftUp batch 3There has been a massive increase in inquiries since DK2 came out. People are most likely a little disappointed by the fake FullHD Pentile panel. It is now possible to reserve or pre-order RiftUp batch 3 units at http://riftup.vrunion.com/

I hope we can now start giving something in return for all the support.

It won't be our next Oculus Rift replacement so long awaited. RiftUp! can be serene for some time

IGZO display could have nearly doubled battery life if used right. Major mistake iPhone 6 don't have those. Some of Apple employees are going to loose their Jobs pretty soon again. This is not the pioneer/innovative company it used to be. Asia companies are supposed to copycat Apple. Not the other way around.

We have already display and board of astonishing parameters. Far superior to RiftUp FullHD. The only problem right now are very large MOQs (10 000s).

I'm working on getting a better deal night and day and so does Daniel.

We have already display and board of astonishing parameters. Far superior to RiftUp FullHD. The only problem right now are very large MOQs (10 000s).

I'm working on getting a better deal night and day and so does Daniel.

So, it is possible, that 3rd batch will include new screens, or it's just an announcement of the future upgrade kit? If so, how would you describe awaited terms, when production of these new kits would start?

The purpose of wondering is to decide - is it worth ordering RiftUP now, or it's better to wait for a couple of months.

Also, if it (new panels) is not in the nearest future - what is your prognosis of 3-rd batch production start?

There is now a bit of a problem with judder on the DK2 for triangle counts greater than demo scenes. It could pan out that the DK2 may have to be shelved as a promising idea, but bad implementation.It looks like OVR are not going to open source their runtime software for the communityto have a go.

This is an opportunity for Rozsnyo to sell more of his kits. Maybe the RiftUp is the wrong solution, just sell standalone kit.

Last edited by cgp44 on Sun Sep 14, 2014 9:45 pm, edited 1 time in total.

The touch screens are now glued to the displays. You cannot apply heat to them without destroying thedisplays. Crack the glass (the display substrate never cracks) you buy a whole new screen, good for sales.

Last edited by cgp44 on Thu Sep 18, 2014 7:15 pm, edited 1 time in total.

@Dr. Beef.......I have had some great success with Riftup and Tridef ...just got it to work perfectly with Falcon BMS. A fantastic experience ...The best VR flight sim of all my flight sims and I have many. Prepar3D is almost there ..they will be coming out with a plugin in a week or two to clinch it...but I digress....It seems DK2 users are not able to have any luck with Tridef ...I think they would kill for it to run with just head tracking. Our Riftups are recognized by Tridef why aren't the DK2s? I know you have a DK2 on the way, maybe you could figure it out. People are getting very frustrated over at the Tridef forums....No answer from Tridef in months. I just want others to have the same experiences that I am. The flight sim community would love it. I dont mean to blow wind up your skirt but you have made many happy here ....

GOOD NEWS! New 7" 1200p (1200x1920) panels and boards with HDMI input are now available for $199 US at mkt.com/vronline

@willibeu Thanks for posting

willibeu wrote:

@Hornet...I agree about positional tracking ..although it will be useful in a cockpit when the resolution is bumped up in CV1. .............. To Get Riftup working with Vorpx.......you can download this free hex editor http://www.mh-nexus.de ...Open the editor then click on file and then open...navigate to your ovrservice folder ...for me it is C:\Program Files (x86)\Oculus\Service . Open the exe ....now do a search with the find option ...search for DK2HD. Take note of where it is. Then Search for DK2 ..copy the hex value for DK2. Then replace the hex value for DK2HD with the DK2 hex value and add four zero's after it. Hex value for DK2HD is 44 4B 48 44 32 For the DK2 its... 44 4B 32 . The new value should be 44 4B 32 00 00 . Enjoy Vorpx !!!

To be honest, the community knows it should drop the Rift after the company sold to fb and went dark side to greedy corp monetizing the humans.

All of the "fan boys" should know that the company they were fans of is long gone.

@DrBeef: Thanks for the nice post. Does this work with any non-rift panel as long as STM32 is there?

DrBeef wrote:

Extract the attached executable, drag and drop the OVRService onto it, it will create a patched version with a .ritfup extension. Replace the current one in your Oculus/Servicefolder with the patched one (rename the existing one and remove the .riftup extension from the patched one), and run it.

If, when you open the Config Utility it now shows a DK2 instead of a DKHD2 prototype, then it worked and you should find you can now run VorpX.

I am very grateful I purchased the RiftUP!, as I would be screwed now with the DK2.I would be in the situation of waiting for OVR to fix the current issues.I would not be able to continue my work which is parametric modelling that I havejust added the OVR sdk 0.3.x output to their xml format input. The XML input format is very limited, but useful formodel immersion which is FAR FAR better than a 2D screen, using Animation Master.The issue for me is as soon as I output a moderate amont of triangles into the scene, the DK2starts juddering to hell. I think I tried the extended mode etc, but got fed up and went back to the RiftUP!

This mentioned, I would suggest that you guys don't get too hasty to play with sdk 0.4.2.Play with 0.3.x in the mean time.

This mentioned, I would suggest that you guys don't get too hasty to play with sdk 0.4.2.Play with 0.3.x in the mean time.

I've been using SDK 0.4.2 with my RiftUp! since it came out and is seems ok to me so far. I've not had any insurmountable issues with it.

The only hack I've had to do was to use the patcher to modify the OVRService so that it can pretend it is a DK2 for the sake fo VorpX, otherwise it is working just fine with anything I try (though I have had to disable the Legacy Mode tick box when running anything built against the 0.4.2 SDK).

@DrBeef: Thanks for the nice post. Does this work with any non-rift panel as long as STM32 is there?

The STM32 doesn't work since firmware 0.4. Only with 0.3. Any software compiled with 0.4 (and therefore requiring the runtime) will not work.

Maybe with a USB dump of the handshake between an original DK1 and the new firmware, the code could be updated.

That happened to me. If we are on the same page. The edid display announcing of the DK1 tracker in the RiftUpis blocked from cluttering up the PC's extended screen. How did DrBeef overcome this? Did he overwrite theidentity of the DK1 in the tracker firmware with the DK2 id.

Last edited by cgp44 on Fri Sep 19, 2014 4:10 am, edited 1 time in total.

I've been using SDK 0.4.2 with my RiftUp! since it came out and is seems ok to me so far. I've not had any insurmountable issues with it.

Very interesting RiftUP OK with the runtime. Was this for games with large amount of graphics, ie didyou fps go lower than some critical amount (75hz, 40hz?), or have you a beasty GPU.

The RiftUP of course does not have the DK2's low persistencty implementation of the 350 line bandingwhere each frame line is kept lit for only 20 per cent of the frame time instead of on all the frame time, whichmake a moving band going down the frame.Suspecting that this with lower frame rates is causing the juddering issue which is the screen flashing.

yes, well, actually all I did was change the string "DKHD2" to "DK2.." (where the . is 0), so when it returns the string any process reading it thinks it is a DK2 attached (including the oculus config util).

Though to be honest, it was working ok before that too. I have a GTX 780, so a pretty good GPU (and suddenly feels dated with the latest anouncement of the 980)

That's what happen when you post asleep.I meant that the STM32 firmware doesn't work with SDK 0.4.

And when I say STM32 firmware I'm referring to Yetifrisstlama's running on a STM32F3Discovery board. No original DK1 involved.Is there another out there we can use?

cgp44 wrote:

That happened to me. If we are on the same page. The edid display announcing of the DK1 tracker in the RiftUpis blocked from cluttering up the PC's extended screen. How did DrBeef overcome this? Did he overwrite theidentity of the DK1 in the tracker firmware with the DK2 id.

The problem is that the SDK 0.4 runtime doesn't detect the STM32 at all. It says no device is plugged.Something in the STM32 firmware responds differently than an original DK1, that's why the USB dump is needed, to compare the values.

DrBeef wrote:

cgp44 wrote:

How did DrBeef overcome this? Did he overwrite theidentity of the DK1 in the tracker firmware with the DK2 id. Edit: he answered me before I submitted the post.

I just hacked the ovr service, rather than the firmware. The firmware is still the same one we originally modified after the RiftUp was released.

In this case, the OVR service is detecting the tracker and just the type detected is being changed.For the STM32, it's not being detected.

What's / where's this RiftUp firmware?The RiftUp is using an original DK1 tracker, isn't? What I saw was just a hack to change return of the Display Descriptor with the new screen parameter, and not a complete firmware to write to an STM32.

Sorry I was wrong in my assumptions. I had turned the OVR runtime service off, hence there was nodirect mode connection with the tracker. I should have tried the RiftUp! with the service running to seeif it was ok, but I had had enough with 0.4.2's setup. I should have tested the theory that the low persistence350 line frame banding was the cause of the screen flashing/juddering, but DrBeef has done this partially for me.

@DrBeef have you a game that can be put into low framerate on your gtx780 to check if everything is still smooth?

Who is online

Users browsing this forum: No registered users and 6 guests

You cannot post new topics in this forumYou cannot reply to topics in this forumYou cannot edit your posts in this forumYou cannot delete your posts in this forumYou cannot post attachments in this forum