Sorry about any confusion with the tutorial, there have been a few changes since then. The node named “OutSideTick” is no longer needed now that all blueprints have access to the “Event Tick” node. So in the case of this part of the tutorial you can simply run a normal tick event into the “Set Actor Location” node to drive the position of the camera.
Now that the tick issue is cleared up, you can ignore the top set of nodes (Event Tick > Get All Actors Of Class > ForEachLoop > OutSideTick). One more quick note: You will need to pull off of the Return Value pin (blue pin) of the “Create Widget” node to see the “Add to Viewport” node pop up in your quick search.
I have not had a chance to update the tutorial for 4.7, however everything should work just as well in the new versions of the engine. There are a couple of minor differences such as what I mentioned in my previous post and a couple of name changes to the default blueprints. (MyCharacter for example was the old default name.) The default Character blueprint for the first person shooter is no FirstPersonCharacter. You will need to use this blueprint in place of MyCharacter (same thing different name). If you need any further help with this tutorial please feel free to post them here and I will be more than happy to help. This way if anyone else has the same issues they can find this thread.
I cant get this to work no idea what i’m doing wrong, I’ve tried compiling without the 4 nodes from your tutorial (Event Tick > Get All Actors Of Class > ForEachLoop > OutSideTick) to no avail (A white box is drawn not the level and the green throbber doesnt follow the player), in addition to trying to include these 4 nodes that throws up an error at compile time.
I’ve included images to show you what they look like currently:
please help as I’m tearing my hair out trying to figure this out!
I have a few corrections for you. However, I will need to get a screen shot of the designer tab of your widget blueprint as well as a screen shot of how you have your material and how you have your textures set up.
Correction one:
As I said in my previous post you can just use the tick event now. The yellow is the correction and shows you how to connect the tick event.
This shows why your previous setup was not working. In yellow you will find: The nodes were not set up correctly. The custom event did not have the target that it needed. In Red: This is one of the things that has changed since the tutorial was made. The nodes that have been crossed out were used to send a tick event to the camera blueprint. (the camera blueprint did not used to have it’s own tick event) I set it up this way to “barrow” the tick event.
However is there any way of getting the throbber to move instead of the actual camera, so a constant pic of the map in the background but the throbber instead indicates the players movement in relation???
The issue I’m having now is the minimap starts by displaying only half the actual map, with the other half showing the rest of the world as white space.
I’ve tried moving the (Minicam) camera about so that it shows the rest of the map from the start, but its not having it.
Which element do i need to adjust so that this works, is it the minicam, the minimap widget or the map rendering.
I would recommend backing the camera out until you can see all of your level. I would then place your image inside of a canvas panel and then resize the canvas panel to clip off the white edges. From there you can go to the transform section of the of the canvas panel and scale it until it looks correct. I hope this helps.
