Forum Replies Created
-
AuthorPosts
-
vkleinCustomer
I would also appreciate an image tracking AR solution, at least use the image/QRCode to initially place the 3d content then let SLAM take over the tracking, possibly corrected from time to time if the image tracker has a near 100% confidency of the actual track.
vkleinCustomerThanks for the working example. It’s not some problems with the Quest or the v71 update. The actual Ver3D Virtual Reality demo has graphics errors. Your demo is working and looking fine. Must be a version prior to the one which started the problems with.
Let’s hope they can fix the problems soon, I have a customer in need of a mobile VR web solution.vkleinCustomerOk, directly from the store, it shows a Enter Vr button. Didn’t show up when started from the projects. But after clicking and accepting inputs does not work, and transparencies /AO are broken. AO pass? superimposed over the floor, chair on the side have their transparency/Z inverted.
- This reply was modified 1 month ago by vklein.
vkleinCustomerI am not kidding, there is no “Enter VR” button on my Quest, newest Update, with the Verge3D demo.
vkleinCustomerDevelopers? Please? There is no Enter VR button with your newest “Virtual Reality” demo project native on a Meta Quest 3 browser. Firmware v71 on the Q3.
vkleinCustomerThat’s not right. It’s much more that that. You would know if you once picked up a Quest 3/pro and used it more than 5 minutes.
vkleinCustomerYes, very funny. If that button would be there like on my desktop browser with Quest attached per link I would press it.
vkleinCustomerCome on guys, tilde works mostly only on English keyboards. Couldn’t you choose another key to press 3x? what was the keybinding for stats before? It worked good.
vkleinCustomerYou are totally right, renaming them by menu or F2 sets the Label and not the Name, that was my error. V3D is using “Name” and works like it should, thank you a lot.
vkleinCustomerThanks, happy to hear that, your support is great.
vkleinCustomerI have this problem too with absolutely no geometry change or incoming/outgoing objects before, during and after the camera tween. In v3d 4.3 and 4.4.
vkleinCustomerTHANKS, I can circumvent this problem for my actual project by not using a normal map on the morph object, so you do not need to hurry for me, but of cause you need to fix it in the long run.
vkleinCustomerIt’s a morph object with a multi-material and one of then has a normal map assigned. I’ve nailed it down to this normal map. Here is a downloadlink or the 3dsmax 2021 file+the map (3.8 MB):
https://download.mediaprojekt.eu/index.php/s/QkjBWCC5bKx2aCB
With map -> error on gltf / sneak peak export.
Clear the map -> running exportvkleinCustomerI managed to basically solve the problem by opening the material in the Node Material editor instead of the old one (which for some scripting/material related custom scripts reasons I use quite often), here the textures get the v3d texture properties attached without problems.
vkleinCustomerOr Verge3D could simply do what it’s told to do as soon as it’s executed the other things in que instead of ignoring code.
-
AuthorPosts