but moving things a slight amount also works
Statistics: Posted by SolarPortal — 31 Aug 2017, 12:15
]]>
]]>
]]>
Turns out that adding an entity to the scene or duplicating especially with multi selection was doing more unnecessary calls than it needed. This could in fact speed up duplication on large numbers on entities. Not a lot, but it will make an impact.
The duplication routine was working as expected which is what had me miffed but it was the extra calls due to the entity list being edited that added more work than it needed lol
Statistics: Posted by SolarPortal — 13 May 2017, 17:10
]]>
currently trying to fix a load lockup with the paths when load the scene.
Edit: Lockup is now fixed and path loading time improved as it only updates the nodes 1 at the end rather than per node being added.
Statistics: Posted by SolarPortal — 13 May 2017, 13:39
]]>
Statistics: Posted by SolarPortal — 13 May 2017, 11:11
]]>
]]>
Going to look at the camera flipping back at the end of the track.
Statistics: Posted by SolarPortal — 12 May 2017, 21:51
]]>
Will look at the spline node editing at the same time.
We have decided we will be doing a release before the upgraded core release as there has been some complications in the upgrade and a few errors caused, so basically got to start from working version again and copy code in without getting the errors.
For now, the camera trigger will get you around it
Statistics: Posted by SolarPortal — 12 May 2017, 13:45
]]>
The spline path is set to line.
I will use the trigger as we discussed months and months back when I had a camera on a spline path zoom into a soldiers head then activates the fps player.. same principle of using a trigger with the camera..
Thank you
Statistics: Posted by epsilonion — 12 May 2017, 01:43
]]>
A way around this for now is to add an extra node that extends the path a bit more and use a sensor or trigger volume to stop the camera moving using that trigger volume.
As for the node not clicking again, StarFire has already told me about this one as she also experienced it the other day. It is caused by the road system being added back in again and the gizmo for secondry edits that are not the main gizmo was rewritten, so this will be fixed asap.
A lua function can be added to control the camera paths a bit easier from the camera.function() library.
Hope this helps
Statistics: Posted by SolarPortal — 11 May 2017, 22:59
]]>
press button 2 and it follows a path to another object and looks at it etc.
The problem I am facing in this test is that at the end of the path the camera faces away from the object at the end of the path and looks back upon the path it has just transversed.
I plan on having a camera and path for each menu Item and to replace the placeholder objects with better ones..
A better way of doing thin would be instead of having a path and camera for each menu item would to be able to assign paths to a camera.
When going back to the main menu from a sub menu it would be ideal to be able to reverse path and to make the camera look in the original direction.
Also I have in the scene script show cursor and since I have put that in I can no longer select path nodes.
Statistics: Posted by epsilonion — 11 May 2017, 22:42
]]>
Statistics: Posted by SolarPortal — 11 May 2017, 20:48
]]>
Statistics: Posted by epsilonion — 11 May 2017, 19:13
]]>
Edit: Here is the default scene in case yours is broken:
Gen2_Default _Scene.zip
To be extracted and overwrite the files in "Data/Scenes/"
Statistics: Posted by SolarPortal — 10 May 2017, 22:47
]]>