Jump to content

davide445

Verified Members
  • Content Count

    140
  • Joined

  • Last visited

Community Reputation

16 Good

1 Follower

About davide445

  • Rank
    Builder

Recent Profile Visitors

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

  1. Discovered the problem, was not using the correct UE level, so now is working fine
  2. Using the standard Cosmos and testing with UE 4.25 and 4.26 I can enter in VR but no controller is shown. Just using UE provided VR test template (arriving here as troubleshooting step for another UE-based VR app) I can move using a standard joypad, instead the controllers didn't show up and clicking any button didn't make any difference. SteamVR plugin is enabled, Cosmos is added in various Action Mappings and Axis Mappings, Controller bindings was regenerated, I tried to attach a MotionController to SkeletalMeshComponent, with no luck. There is a specific problem btw Cosmos an
  3. @HackPerception thanks for this. To better understand, the controllers are tracked only using the headset cameras, so that only optical features are usable? Was thinking that if they are using also some kind of other tracking system that can be influenced from magnetic field this can be also a problem with a big metal mass nearby. If it's only feature extraction tracking I will attach to the wall bigger A4 sized printings of some codes (better kind of QR code or big simple geometric shape are better?) . Curtains are in fact black window shutters so that need not to be a
  4. For a project we are using a treadmill as in the image and Vive Cosmos. To improve headset tracking I closed widows curtains and attached stickers to the wall, set up the room staying on the treadmill so that the headset can setup his reference points. Seems to work well. What I have problems are the controllers that often loose tracking, even if they are just in front of me and not occluded from the treadmill structure. Wondering if this does have something to do with the treadmill or we can improve this in some way.
  5. Yes with beta release motion compensation it's available
  6. As in the title we are developing a customer project based on Cosmos and wanted to have a try to motion compensation in case we will need it. The Vive Console told me cannot enabled due the fact our graphics card didn't support this feature. In the guide is written will be available for any Nvidia card better than GTX 1060, so that I'm wondering if there is anything else I need to consider to test it. Latest Nvidia driver is installed.
  7. @C.T. done, using a new account since testing a brand new Cosmos to be used for a project.
  8. All is working fine for my in and out VR testing sessions, but after a while the Vive console show there is an error (! icon) and controllers start having problems in pairing (sometimes is possible some others not). In the worst case I need to restart Vive console, not a problem for me but a problem doing demos with customers. Attached the logs, will be good being able to track down the problem. @C.T. viveVRHelper_20210115.txt vrcompositor_20210115.txt vrserver_20210115.txt
  9. Since about a month the left controller first refused to connect, after using the reconnect feature connect but after few min disconnect. The right controller work fine. Swapped the batteries with new just recharged, firmware the latest one not beta. Any suggested path to check what's going on.
  10. This is not what I have written, so didn't know why happens to be in my quotation. Someone else later deleted his post?
  11. @zzywas meaning hardware compatibility, with current headset generation.
  12. @zzy we will decide today with the customer, but after (again) reviewing current hand tracking status I think the orientation will be to stick with HTC Vive headset and just use the controllers, waiting the whole technology to mature as a following option. About future hardware, I hope v1.0 will back compatible? Our project is due to start this year and I didn't see any announcement for new upcoming headset from Vive.
  13. Quest 2 has a lower refresh rate so far, will see in the future when will reach 90hz. For corporate applications such as I'm interested about has as primarily target hardware this mobile chipset, something not all realtime engine focused on industrial applications are supporting (they need powerful hardware you can find only in a real PC). Also does have in my view the "Facebook little problem" about data. HP Reverb G2 is a Windows Mixed Reality solution with a compatibility layer with SteamVR applications. I didn't find nowhere someone disclosing how well this is working. I read a test w
  14. Ah ok something I know. Yes Oculus tracking is supposed to be better even if I'm satisfied of the Cosmos for my non-gaming needs, but the Rif S has less resolution and the Quest is an autonomous headset by design so really not comparable and so far with lower refresh rate, even if with the Link the thing start to blur. To be honest as corporate user I stay away from Facebook and his data hungry policy. Good to know what was you referring to, thanks.
  15. Out of curiosity, what are these headset? I'm supposed to know all the major and minor brands for my work, and didn't remember any cheaper more "powerful" one in the same category...so curios to know if I miss something. Powerful you mean in term of resolution or frequency rate?
×
×
  • Create New...