Skip to content
This repository has been archived by the owner on Mar 28, 2024. It is now read-only.

[BUG-8771] Second Life Oculus Viewer don't move when using GTX970M #16354

Closed
3 tasks
sl-service-account opened this issue Mar 13, 2015 · 8 comments
Closed
3 tasks

Comments

@sl-service-account
Copy link

sl-service-account commented Mar 13, 2015

Steps to Reproduce

I connected Oculus rift DK2 to PC and open the viewer above.
And I tried to go to HMD mode.

Actual Behavior

When I open SL Oculus Viewer for windows and click the HMD mode button,

It says "cannot enter HMD mode because your graphics card does not support the minimum requirement Vertex Shaders and Vertex Buffer Objects
are required for proper rendering in HMD mode."

I cant understand why this happens because my graphics card is GeForce GTX970M.
this should exceed the minimum requirement.

Oculus viewer
http://wiki.secondlife.com/wiki/Release_Notes/Second_Life_Project_OculusRift/3.7.18.295296

Expected Behavior

I expected to go to HMD mode and My rift would display SL world.

Other information

I cant believe gtx970M doesnt have VertexShader.

Attachments

Links

Duplicates

Related

Original Jira Fields
Field Value
Issue BUG-8771
Summary Second Life Oculus Viewer don't move when using GTX970M
Type Bug
Priority Unset
Status Closed
Resolution Expected Behavior
Reporter NaokiCamber (naokicamber)
Created at 2015-03-13T18:18:17Z
Updated at 2016-06-30T22:20:22Z
{
  'Business Unit': ['Platform'],
  'Date of First Response': '2015-03-13T15:24:24.674-0500',
  "Is there anything you'd like to add?": 'I cant believe gtx970M doesnt have VertexShader.',
  'Severity': 'Unset',
  'System': 'SL Viewer',
  'Target Viewer Version': 'viewer-development',
  'What just happened?': 'When I open SL Oculus Viewer for windows and click the HMD mode button,\r\n\r\nIt says "cannot enter HMD mode because your graphics card does not support the minimum requirement Vertex Shaders and Vertex Buffer Objects \r\nare required for proper rendering in HMD mode."\r\n\r\nI cant understand why this happens because my graphics card is GeForce GTX970M.\r\nthis should exceed the minimum requirement.\r\n\r\nOculus viewer\r\nhttp://wiki.secondlife.com/wiki/Release_Notes/Second_Life_Project_OculusRift/3.7.18.295296',
  'What were you doing when it happened?': 'I connected Oculus rift DK2 to PC and open the viewer above.\r\nAnd I tried to go to HMD mode.',
  'What were you expecting to happen instead?': 'I expected to go to HMD mode and My rift would display SL world.',
}
@sl-service-account
Copy link
Author

Whirly Fizzle commented at 2015-03-13T20:24:25Z

Heya Naoki,

The rift viewer has not been updated for a while and still uses the old gpu table to detect the graphics card.
Your card is not in the gpu table - see BUG-7322

For now you can try the following:

Go to the install folder for the Occulus viewer and open the file named gpu_table.txt in a text editor.
Add this line...

NVIDIA GTX 970M							.*NVIDIA .*GTX *97[0-9]M.*							5	1	0	4.4

Save changes to this file and login.
Hope that works :)

@sl-service-account
Copy link
Author

NaokiCamber commented at 2015-03-14T03:56:14Z

Thans for your kind help.
But it doesn't work.
In BUG7332, there are people who can't solve this problem by adding the line above too.

1.It doesn't matter where I add the line in gnu_table?

2.Do I need to add the correct name?
In other words, the difference between ".*NVIDIA .GTX *97[0-9]M." and ".*NVIDIA .GTX *97." affect the Result? My VGA name is GeForce GTX970M.

@sl-service-account
Copy link
Author

NaokiCamber commented at 2015-03-14T04:18:30Z, updated at 2015-03-14T04:23:42Z

And when I change to Intel HD Graphics 4600 from GTX970M to display this viewer and I open the viewer,
viewer says "from ATI GeForce Lulz to Intel HD Graphics 4600".

It means oculus viewer misunderstand that 'GTX970M' is 'ATI Geforce Lulz' doesn't it?

@sl-service-account
Copy link
Author

Whirly Fizzle commented at 2015-03-14T04:41:00Z

I think 'ATI Geforce Lulz' is just what the viewer will call any card it does not recognise. (Someones idea of a joke ;))

I'll ask Tank (he maintains Firestorm gpu_table, we dont have benchmarking yet) to look if I gave you the wrong regex for the 970M.
Thats the line used in Firestorm viewer gpu_table for your card.
I think manually editing the gpu table in the Occulus viewer should work around this problem though.

@sl-service-account
Copy link
Author

Whirly Fizzle commented at 2015-03-14T05:01:30Z

Naoki, I attached the gpu_table.txt to this issue which should detect your card.
If you replace the gpu_table in the viewers install folder with the one attached to this issue does that work?

@sl-service-account
Copy link
Author

NaokiCamber commented at 2015-03-14T06:21:29Z

That works!!!!!
Thank you, Whirly

when I manually edit the content of gpu_table.txt, I can't solve the problem.
But when I copy your file and paste(overwrite) it, I can do that.

I have suffered from this problem these days.
Finally I can overcome this problem thanks to you.

@sl-service-account
Copy link
Author

Whirly Fizzle commented at 2015-03-14T19:07:39Z

Yay!

Once the Occulus viewer is merged up with viewer-release, this should no longer be a problem. The gpu table is no longer needed with the benchmarking feature.

@sl-service-account
Copy link
Author

Kyle Linden commented at 2015-03-18T20:40:29Z

Hi Naoki,

Thank you for reporting this issue. Thank you Whirly for walking her through updating the gpu_table.txt file to work with the Oculus Project Viewer.

Thanks!

Sign up for free to subscribe to this conversation on GitHub. Already have an account? Sign in.
Projects
None yet
Development

No branches or pull requests

1 participant