ideas please

[hiltropper]

hello again
would be really nice if someone had any ideas to make my code more precise.
it is a code for a battery that can be saved as phunlet without any problems (but needs a special laser to work right).
nothing wrong about everything but the discharge timer.code:

Code: Select all

(e)=>{
    textcolor = [sim.time, textcolor(1), textcolor(2), textcolor(3)];
    sim.time > (math.toint(textcolor(0)) + 0.97) ? {textcolor = [textcolor(0), (textcolor(1) - 1), textcolor(2), textcolor(3)]} : {textcolor = [textcolor(0), textcolor(1), textcolor(2), textcolor(3)]};
    textcolor(1) <= 0 ? {textcolor = [textcolor(0), 0, textcolor(2), textcolor(3)]} : {textcolor = [textcolor(0), textcolor(1), textcolor(2), textcolor(3)]}
}

as you can see , i use the sim.time and the integer sim.time +0.97 , every second the battery discharges 1. now whats the problem : low cpu notebook : 0.97 is right . high cpu pc : 0.99 is right ,at 0.97 the step is much more than 1.the timer depends on the fps .
no problem ,if you really want to change the value everytime you add another geom and the frames go low...
i don't expect another code ,i know them. if it were possible ,i would like my code corrected.
any ideas?
thanks.

[Kilinich]

it's really hard to understand what's the problem and what you need...

[TC42]

I have no idea what you are talking about... but I can guess
So you have sim.time + 0.97, so that on your PC, it discharges 1 every second. The problem is that the timer depends on the fps. If I'm right... you can set the system frame rate from inside algodoo
(devious and possibly evil? Yes. Will I download a scene that does that? Nope.)
So what you need to do is adjust the integer added to sim.time depending on the frame rate... Kilinich (or gradyfitz)do you have any ideas how to read the frame-rate?

Other than that, I suggest that you make it automatically increase the sim.frequency when you open the scene.

[hiltropper]

tc42 you are right.
sorry for that cryptic post i guess i had no time when i did it.

Other than that, I suggest that you make it automatically increase the sim.frequency when you open the scene.

is that possible if my cpu is to weak to do that? i mean this actually is the problem ,the script is the same but the faster the cpu the faster it discharges...

[TC42]

Yes, increasing the sim.frequency will cause more lag, but results in a more accurate simulation. If you're using laser, then I suggest that you discharge the batteries mechanicle-scriptedly (spelling??) using a box/circle on a hinge that collides with something else (which has the discharge code in the oncollide menu) when the hinge is running. This way, the discharge rate will be more stable on PCs of varying power.

[Someone Else]

Presonally, I (or davidz40 for that matter) would use an alternating collider. This is the code I would probably use:

Code: Select all

collideWater = !collideWater

The coded geom should be a circle, hinged between two boxes. It should overlap both boxes. More overlap = more reliability, but more unwanted vibration.

[hiltropper]

thanks so far if i get new results i will report it here.