Trigger help please.

[epsilonion]

[CreativeOcclusion]

[ant0N]

Hi!
I did not find you the function: entity.callFn(..)
I think you have error in another script.

[SolarPortal]

[epsilonion]

It was ment to be like a pop up dialogue box with information about the game.

Several trigger boxes on the scene with different info on the pop ups so it isn't a hud per say but looking through the doc's couldn't see another way of doing it apart from displaying a picture and hit space to continue, tbh I don't know which would be easier lol

[StarFire]

You could display a simple gui for the "About" called from the lua trigger event as you can display multiple ui's

[epsilonion]

Thats what I am trying to do lol,
its also started giving Particle Univers errors once I added the Hud..

[epsilonion]

This is what I am trying to display when the player collides with a trigger

I am trying to display this picture as information on say a tutorial.

trigger to show.

newgame.png (238.15 KiB) Viewed 22034 times

Attached is the scene file that I am trying to do it on, I already have a pause menu that seems to work when you press the P key (would rather that be the Escape key but that exits the game),


Errors:
The particle Universe errors came about when the FPS Hud was put in the scene.
If you rotate the FPS player to face a different direction the camera seems to rotate and the gun is no longer in front of you.
Every now and then after running the scene the terrain seems to go 1000% on the specular, reloading the scene seems to fix it for a short time.

Scene File:

[CreativeOcclusion]

[StarFire]

I will hunt down the errors once the new FPS player redesigning is started. I think they are Lua errors so could be removed, although I could be wrong without having a look. If not we could reduce the error message sensitivity to stop them completely for you.

[epsilonion]

Just updated that post with scene file, gui, scripts etc..

[StarFire]

Hey Liam, just found your problem and fixed it. We had put in a performance catch for all states other than the standard states, this catch prevented any scripts from running if the object was hidden(visibility) but with triggers and other volumes they are made invisible by default when playing the game thus no scripts could run on them. I have tested your scene on the new build and its now working fine.
The fix will be in the next update for you

[epsilonion]

Thank you very much..