Ok, now I managed to test all cases with the update. Everything is fixed. Thank you so much for the amazingly quick fix!
I am having an issue getting the “Build Solution” in VS2017 to show 2 succeeded. I must have messed up one of the steps in the tutorial but I don’t know what. I am new to VS so my language may be a bit off here when explaining
At the start of the build it skips one: Skipped Build: Project: UE4, Configuration: BuiltWithUnrealBuildTool Win32
The very first time I attempted the build I got an E0018 error and tried the fix listed here, and here is a quote of it:
I am unsure if is was related to my issue, also, I do not know if it has any effect, but VisualStudio is set for Win64 on the Platform Solution box at the top. Would that cause it to skip Win32 thing that it is mentioning?
Thank you in advance.
Update: I changed that line as recommended further down on the same page I linked
I have no errors, but it is still skipping the “Configuration: BuiltWithUnrealBuildTool Win32”, I saw the final post on that link mentioning that having Unreal saved on C drive fixed his problem. I have VS on C and Unreal on another drive. I really don’t want to have to put all of on my primary drive, but is that what is causing ?
It shouldn’t be building a 32 bit binary at all with a win64 target.
Rebuild your win64 and paste the output log text to pastebin and post a link, its more likely that you have visual studio configured wrong.
Thanks for the quick response, here is the link
Looks like it compiled fine from that log? Is it not available in your plugins selection?
I’ll look into and post my findings here in case anyone else has the same issue.
Thanks a ton for the detailed info. I’ve added the ‘Set Replicated Movement Mode’ node to the Vive pawn after Begin Play and set it to ‘LowGrav’, but it doesn’t seem to take. Movement still works as usual. Is there something else I need to adjust perhaps?
It is showing, and I think it is working correctly. I think I have been misunderstanding what “skipping” means in VS. Since the last line of my output log (1 succeeded 0 failed 1 skipped) did not show exactly what was shown in the last step of the setup guide (2 succeeded 0 failed 0 skipped), I had assumed I was going to encounter problems.
Thank you for checking for me, much appreciated.
No, that should be it, try printing out the current movement mode and making sure that it switches over.
Hello, I am very new to UE4. Your template is great and your development videos are really interesting to see how you are working things out, keep it up!.
I would like to know if anyone could help me figure out how I can adjust the [L Hand D Pad Press Based Movement] inside the Vive_PawnCharacter BP so that when I have DPAD Orient in play mode active I can rotate instead of strafe.
Appreciate the help!
Ivan
Call: PerformMoveAction_SnapTurn with a positive or negative value, if you want smooth turning then you multiply your turn rate per second by the current delta time and pass it in.
Im working on a VR arena for the Oculus Quest, but until that becomes available I have been testing on two Rifts running on separate computers over wifi with a third computer running as host, the problem is when one client fires a gun that activates the haptic event in the MotionController thats gripping the Gun, and for some reason the other client can feel the haptic aswell.
I heard every client thinks of itself as player index 0 so how can i get the Player Controller of the specific player holding the weapon?
Thanks for making the template!
Well that node is set to run on OwningClient, so normally it would be working fine as is? I am not sure where you are calling that function from though and you may be running haptics in other locations or somehow calling that node on all characters and not just the gripping one? You don’t normally need to run haptics as a replicated node though, generally you would have an OnFired or OnUsed event that you could have the GUN fire off haptics from or notify the character to fire off haptics when it happens.
PlayerController 0 IS the local player on every machine, you are right on that.
On gripped objects you can also check IsHeld and pull off the motion controller that is returned and test “IslocallyControlled” on it, that would let you know if the holding motion controller is local or not. shouldn’t be needed in specific case, but its something useful to know.
I have been trying to learn from the 4.21 template but none of the pawn BP nodes visibly fire. I couldn’t find much on the issue other than one post from 2015 saying the answer is to not use the Player Start, and instead just drag the pawnBP straight in and set the GameMode option to possess that pawn at start. did seem to work for the blueprints not firing, but also on play causes me to drop in several feet away, outside my body, at an odd rotation. I am still very ignorant on UE4, so I am not sure how to get the pawn working right without using the Player Start.
Has anyone else here been able to use the PlayerStart and still be able to visibly see what nodes are firing on any of the pawns in the template?
? You may be looking at the wrong pawn, the game mode spawns the Vive_PawnCharacter when VR is detected (the name is a holdover from very old versions, its more than just for vive).
It is debuggable just fine, and as for the Player Start thing, I have avoided making a game mode override which would be required to override player start behavior and offset spawn locations because I haven’t felt it was a big enough reason to override yet another class for. Manually spawning at player starts also works fine, or even offsetting locations post spawn. The spawn location code in engine is sadly fairly well buried and not in the most logical location.
Yes I original tried putting it in the BP_GunActor after OnFire so then I tried putting it in the pawn with the owning client event but both players are using the same Pawn blueprint which is being replicated so i think that’s where my issue lies. pdf was helpfull the isLocallyControlled was also helpful it totally fixed my problem!! thanks!
Hi, I have a problem 
Second grip is not working. When I try to grab with my second controller it just release from the first hand and get the component on the second hand. I want to grab it with two hands like in the template with the gun demo.
Any help?
It should be working with that setup, i’ll have to check against another SG_Free listed item tonight to be sure since that mode isn’t tested as often, but it should be working as shown (the console uses SG_Free_WithScaling_Retain which is essentially the same thing).
Granted that is assuming that you are using the template pawn, if you aren’t, then you have to choose when to add a secondary attachment point instead of swapping grips.
Edit Yeah SG_Free is still working correctly, sounds like maybe you haven’t implemented secondary attachments in a custom pawn? I do not automate much in my plugin, I try to have intervening steps everywhere so people can literally build what ever systems they want.
Thanks for the response. I do not see any nodes firing on the Vive_PawnCharacter in the template, but on the default Unreal VR template they seem to be working but I have other issues on that template. I am unsure what is occurring on each of them so I am just going to start with some tutorials on starting a VR project from scratch and maybe at some point I will figure out what is going on.
As in you can’t debug them? like break pointing them?
No I don’t think so, I suppose it could be considered debugging. Just to see the animations on the BP nodes to see which are firing as soon as I hit play, or teleport, grab things, etc. with the pawn. It makes it easier for me to understand what chain of events are happening, and when. Let’s say I bring up the BP for the ClimbWallActor that moves around; I open the blueprint and watch it when I hit play, and I see the Event BiginPlay fire and the execute lines turn red. On the Vive_PawnCharacter I do not see anything firing the the BP, not even tick events. I have “Should minimize editor on VRPie” unchecked, so the BP stays on my screen when I hit play for VR Preview option.
Sorry, I think my verbiage is a bit off on explaining these things.