2/9 Pt.1 - Disaster

 So far for production today, things have been going awful. 

Mainly, my main drive is only 128gb, which has given me way more trouble than it should be. It has held me back from updating Steam Vr, it throws up 2-3 errors per time I open Unreal, but I'm pushing through it. 

I've fought through it all to get a small scene together after hours of trying to get everything working. The number of hours just watching shaders compile and trying to get through all the Facebook walls just to use my quest after not turning it on in a while is insane but I managed to be sort of where I wanted to be. 

A lot of the struggle this week was getting the pipeline for the new project in place, and now with all that set up and figured out, full production should go alright.

Comments

Post a Comment

Popular posts from this blog

3-22 A final push

Image
 So, did those changes from the last post work? No, but hopefully we can get that to change. For starters, I need to find out what the speed is reading.  This print string node I found will show it on the screen, and it's showing as (0,0,0), which tells me the blueprint is not looking at the right thing. Or, maybe it is? I'm not sure exactly, and after testing some of the other nodes and doing a little research, I landed on this thread from the unreal forums: https://forums.unrealengine.com/t/how-to-i-get-motion-controllers-velocity/97140 and I decided to test the world position of the controllers, which did show up and update so, trying that looks like this: and surprisingly, it works sort of. It outputs around 2 in the Z when I do the reeling motion, so that should be what I need to use when looking for that. The next step was to hook that up to the temporary delete which looks like this:  With the AND node looking at the collision. Now it is time to test this, and... Instant
Read more