bansama

This is very good news!

I mean both of the run options offered in Leadwerks while it's running. They're represented by a full green arrow and an outline green arrow. Doesn't matter which I use, both will cap at 30 fps when sync is set to true. Only when the project is published through the project manager does sync then cap at 60 fps (which would be right for my monitor).

That appears to be it. The old app.lua has that set to false. Still unsure why it only gives 30 fps when run through Leadwerks though. Thanks for helping to clear this up.

Nope. Then I wonder what's going on. My hardware has not changed. They only thing that has is Leadwerks though the normal non-beta updates =/ I've also just tried building a new copy of my old project and that is now capped at 60 fps when published as a standalone. So something has definitely changed in the last few months. Update: Yeah, something has definitely changed with app.lua. I managed to build the project again with the old app.lua script and that one shows fps of several hundred. With the current default app.lua script created by Leadworks, it is showing a cap of 30 when testing through Leadwerks (both Debug and Run) or 60 when published.

I noticed today that I'm only able to get 30 fps when running builds through Leadwerks. But I'm sure this never used to be the case (and old project still gets fps in the hundreds when run outside of Leadwerks). Is there a setting I've missed that allows me to change this?

As someone else said, one of the recent patches was meant to fix the throw function for when a player does not have a weapon. Is this not the case?

With one possible exception, I've never had an update break scripts. I can't even be sure it was an update that did break the script that stopped working... That said, I have had updates wipe out all connections in the Flowgraph. I've also had to manually update all my projects as a new update to Leadwerks only seems to give you a warning that existing projects are out of date. So if you're concerned something will break, there's certainly opportunity to make a backup of the project directory yourself. As for getting a refund from Steam, they do offer a one-time goodwill gesture refund. But you'll have to fight for it and be polite while doing so.

Yeah, I just found this. It only works if I make the trigger object really tall. Perhaps this is connected to the height of the player? This now appears to be working again. I would still like to work out how to use a separate entity to toggle this though just in case something else breaks it again in the future (and it could probably be useful for other things too). That is, to be able to access the variable for enabling/disabling with an imported script. I think I have an idea of how to try this. I just need to wrap my head around self and local variables... Thanks everyone for all the help and ideas thus far.

I have tried exactly as your video, making trigger objects on the pads and adding the script to the triggers. In that case nothing happens. That is, I collide with the trigger and don't teleport. If I add the script to the pads without the teleport, they work as long as their collision type is not trigger (but with the behaviour mentioned at the start of this topic). In short, the Trigger collision type is not working for me.

You probably need to add the included script to Pad 1 and Pad 2, linking to the other pad respectively. The forum was being a pain while I was trying to attach the files.

I'm new to Lua too and wanted to to something similar myself. It probably isn't very good, but my solution was as follows: Script.ObjectDescription = "" --String "Object Description" Script.DisplayTimeMax = 5000 --Int "Display time" Script.Used = "0" Script.DisplayTime = 0 Script.DisplayEnabled = false local font1 = Font:Load("Fonts/arial.ttf", 15) function Script:Use(context) self.Used = "1" self.CurrentTime = Time:GetCurrent() self.DisplayTime = Time:GetCurrent() + self.DisplayTimeMax end function Script:PostRender(context) if self.Used == "1" then App.context:SetBlendMode(Blend.Alpha) App.context:SetFont(font1) self.DisplayEnabled = true if self.DisplayEnabled == true then if self.DisplayTime > Time:GetCurrent() then self.texture = Texture:Load("Materials/Developer/GreenGrid.tex") App.context:SetColor(1,1,1) App.context:DrawRect(598,598,304,104,0) App.context:DrawImage(self.texture,600,600,300,100) App.context:SetColor(1,1,1) App.context:SetColor(0.1,0,1) context:DrawText(self.ObjectDescription, 610, 625) else self.DisplayEnabled = false self.Used = "0" end end App.context:SetBlendMode(Blend.Solid) end end Basically, this allowed me to display a short piece of text with a background when I pressed the Use key over an object the script was attached to.

Even with that stripped down script, the result is the same. The only difference is likely that I am using the default FPSPlayer.pfb. But that has the same Physics mode, Collision type, and script that you are adding to a pivot, so it shouldn't be acting any different. Have you tried your script using the FPSPlayer.pfb? I've tried making a brand new map, using a pivot as the character and again, the same problem occurs. Just in case, I've attached a rar of the new map I just knocked together, along with the script I attached. _temp.rar

Yep. The script acts as if an "exit" is detected when you stop moving and then move again. I.e., teleport and jump, etc. I can solve that by not allowing the script to enable itself, but that makes the teleport one-way. If I then move away from the teleport and re-enter, it won't send me back to the original teleport. The script above is what I think I should work from for the outer pads (the ones I want to use to enable the teleports. The script I am using on each of the actual teleports is as follows: Script.entered = false Script.exited = false Script.hadCollision = false Script.Target = nil --entity Script.Enabled = true --bool function Script:UpdatePhysics() if self.entered then if self.hadCollision == false then if self.exited == false then self.exited = true self.component:CallOutputs("OnExit") --System:Print("Exited") --self.Enabled = true ** this can also be self.Target.script.Enabled = true, doesn't matter it will have the same effect ** self.entered = false end end end self.hadCollision = false end function Script:Collision(entity, position, normal) -- speed self.hadCollision = true self.component:CallOutputs("OnCollide") if self.entered == false then if self.Enabled == true then self.component:CallOutputs("OnEnter") --System:Print("Entered") self.Target.script.Enabled = false --entity:SetPosition(self.Target:GetPosition()) -- Teleports if entity:GetKeyValue("name") == "Player" then EntPlayerCoord = entity:GetPosition():ToString() --System:Print("Player "..EntPlayerCoord) EntPadCoord = self.entity:GetPosition():ToString() --System:Print("Send Pad "..EntPadCoord) TarPadCoord = self.Target:GetPosition():ToString() --System:Print("Targ Pad "..TarPadCoord) end PlayerTable = split(EntPlayerCoord, ", ") --for key,value in ipairs(PlayerTable) do -- System:Print( key .. " has value " .. value) --end SendPadTable = split(EntPadCoord, ", ") --for key,value in ipairs(SendPadTable) do -- System:Print( key .. " has value " .. value) --end TarPadTable = split(TarPadCoord, ", ") --for key,value in ipairs(TarPadTable) do -- System:Print( key .. " has value " .. value) --end -- Will need to use checks like this -- to help cope with minus numbers, etc., when teleporting BaseValue = "0" -- Need to set this to avoid error if SendPadTable[1] < BaseValue then OffsetX = PlayerTable[1] - SendPadTable[1] --System:Print("LT X " .. OffsetX) end if SendPadTable[2] < BaseValue then OffsetY = PlayerTable[2] - SendPadTable[2] --OffsetYa = SendPadTable[2] + OffsetY --System:Print("LT Y " .. OffsetY) end if SendPadTable[3] < BaseValue then OffsetZ = PlayerTable[3] - SendPadTable[3] --System:Print("LT Z " .. OffsetZ) end if SendPadTable[1] >= BaseValue then OffsetX = PlayerTable[1] - SendPadTable[1] --System:Print("GT X " .. OffsetX) end if SendPadTable[2] >= BaseValue then OffsetY = PlayerTable[2] - SendPadTable[2] --OffsetYa = SendPadTable[2] + OffsetY --System:Print("GT Y " .. OffsetY) end if SendPadTable[3] >= BaseValue then OffsetZ = PlayerTable[3] - SendPadTable[3] --System:Print("GT Z " .. OffsetZ) end TargetX = TarPadTable[1] + OffsetX TargetY = TarPadTable[2] + OffsetY TargetZ = TarPadTable[3] + OffsetZ --System:Print ("XYZ: " .. TargetX .. ", " .. TargetY .. ", " .. TargetZ) entity:SetPosition(TargetX, TargetY, TargetZ) end self.entered = true self.exited = false end end function split(s, delimiter) result = {} for match in (s..delimiter):gmatch("(.-)"..delimiter) do table.insert(result, match) end return result end Don't mind the system:prints, I just used those while coding to check what the script was doing. The section commented with ** is where enabling the teleport again is likely causing the problem. This is why I need to work out how best to enable the script again from a different entity. Does this make any sense?

The first suggestion is not going to work, no. I am using the teleports as a way to move players around without their knowledge, so having them specifically hit a button isn't going to work in all situations. The second idea might work, thanks. But again, I could use some help on how best to access variables from an imported script, as half the time I try, they cannot be found (I get the usual attempt to access nil value error).

Yeah, that's the script mine is based on. It has the same problem with it detecting an "exit" as soon as you stop moving even though you're still on the entity.