Jump to content

MoVE_VR

Verified Members
  • Posts

    5
  • Joined

  • Last visited

Reputation

0 Neutral

Recent Profile Visitors

The recent visitors block is disabled and is not being shown to other users.

  1. I've messed around with it and followed the suggested steps and I wasn't able to fix the issue. The eye calibration works just fine, but when I hit play in unity it still gave the same error. Of note though is that when I did the full uninstall/delete and then reinstall it never asked me to accept the EULA. The only thing is asked was the usual do you want to let sranipal make changes to your pc thing. Also, when I opened the vr menu for the first time after reinstalling, the enable eye tracking toggle was already on. This makes me wonder if something is being saved on the steamvr side, possibly from other steam user accounts as there are others that sign in to steam and use the headset occasionally. *Update Edit* I think I've had a breakthrough. I went digging around in their code and found where it was outputting the error from. I disabled the code as shown in the screenshot snip I've attached and the eye/facial tracking was working in their sample scene v2 with no issues. So whatever the problem is, there's nothing wrong with the functionality of the eye tracking. There just seems to be a bug with the EULA agreement prompt process. I would keep trying to get the EULA prompt thing to work, but at this point I could not care less about it. So while this isn't a real solution, it is a workaround. Of course if this has given you any additional insight or sparked an idea to fix it properly, I'd be game to try it out. Thanks! * I had included an image in my response and it's still awaiting approval from moderators so I'm posting my response without it for now*
  2. I've messed around with it and followed the suggested steps and I wasn't able to fix the issue. The eye calibration works just fine, but when I hit play in unity it still gave the same error. Of note though is that when I did the full uninstall/delete and then reinstall it never asked me to accept the EULA. The only thing is asked was the usual do you want to let sranipal make changes to your pc thing. Also, when I opened the vr menu for the first time after reinstalling, the enable eye tracking toggle was already on. This makes me wonder if something is being saved on the steamvr side, possibly from other steam user accounts as there are others that sign in to steam and use the headset occasionally. *Update Edit* I think I've had a breakthrough. I went digging around in their code and found where it was outputting the error from. I disabled the code as shown in the screenshot snip I've attached and the eye/facial tracking was working in their sample scene v2 with no issues. So whatever the problem is, there's nothing wrong with the functionality of the eye tracking. There just seems to be a bug with the EULA agreement prompt process. I would keep trying to get the EULA prompt thing to work, but at this point I could not care less about it. So while this isn't a real solution, it is a workaround. Of course if this has given you any additional insight or sparked an idea to fix it properly, I'd be game to try it out. Thanks!
  3. Excellent post! I've followed all the steps successfully up to "Test if everything works by dragging the SRanipal Eye Framework prefab in your Scene and running the scene." When I hit play in the Unity editor (2022.2.4f1) it gives me an error "[SRanipal] Initial Eye: EULA_NOT_ACCEPT". Which is very confusing because when I look in the log file SRanipal creates, it shows that the EULA has been accepted. I've attached it to show. Do you have any ideas on how I can fix this? Thanks! SRanipalConfig.ini
  4. I'm having the same issue. The eula_not_accept is making this unusable.
×
×
  • Create New...