C2 games and 120hz monitors (*dt problem?)

TiAm

Please avoid OLED displays, they have problems with ghosting which is worse than Plasma TVs. Try ULED instead, which is basically the same thing in terms of colour, expect it doesn't degrade since there are no organic components (One 2008 technical report on an OLED TV panel found that "After 1,000 hours the blue luminance degraded by 12%, the red by 7% and the green by 8%.").

Also, 4K isn't worth it at all. All movie releases are currently in 1080p, only a handful of games can do 4K and that requires what might as well be a render farm to play. To be honest, 4K is just going to be the same thing that "3D" was a couple years ago. Also, forget watching TV on a 4K tv/monitor, there's a delay that can be anywhere from 16 seconds to a full minute. Honestly just stick with a 1080p monitor.

On another note, does anyone know if Events that use speed need to have dt included? E.g. Bullet Behaviour or Platform behaviour?

Nesteris

/Start: Massive Geek Digression

I actually have a plasma, and while they have a vast litany of drawbacks, there is one thing they are uncontested at: TV and movies. In a dark room they beat the pants off any LCD display.

ULED is interesting, but frankly it sounds like it's just a souped-up local dimming + Quantum-Dot solution.

Quantum-Dot TV's have better color saturation than LCD, but can't compare to plasma/OLED on contrast. Local dimming...don't get me started.

The article I read said that the ULED tech was shown off in a brightly lit showroom where the superior contrast of OLED (and, likewise, the blooming caused by local dimming) would be impossible to spot.

I'll agree: 4k movies/tv are pointless for screens that aren't wall sized. But 4k for coding/graphics? Yes please.

OLED blue element lifetime has improved significantly since 2008. At this point: only an issue for monitors running 24/7. Burn is still a concern though (not near as much as with plasma).

The sticking point? Price. OLED is still too damn expensive. 50 inches has to get <$1500 to be competitive, and that's a way off.

/End: Massive Geek Digression

TiAm

Well in any case, you might find this interested and hilarious to read before going out to buy a new TV/monitor.

Here's a quote from the article:

[quote:mw95sp9a]There's also ULED, an ultra LED (whatever the hell that means) that also uses Quantum Dots. When we talked to Hisense, one of the smaller TV manufacturers with way less market share at stake to risk by answering honestly, we were told that ULED and OLED are completely identical, despite the fact that OLED costs more.

Nesteris normally, if there is a unit like "in pixels per seconds"or "in degrees per seconds", that means that dt is not needed (as one pixel per second is still one pixel per second, regardless of the framerate, due to the clear definition of a second on a fixed timescale)

mostly, all behaviors related to movement should not need dt.

Refeuh

Thank you very much! I appreciate that

facecjf great art work, btw, I checked the links in your signature, very nice !

Unrolling the x & y you end up with :

dir.x = Player.ImagePoint.X - Gun.Pos.X

dir.y = Player.ImagePoint.Y - Gun.Pos.Y

dirLength = sqrt(dir.x^2 + dir.y^2)

v.x = dir.x / dirLength

v.y = dir.y / dirLength

Gun.pos.x = Gun.pos.x + Gun.speed*dt*v.x

Gun.pos.y = Gun.pos.y + Gun.speed*dt*v.y

I don't fully understand this but, I think once I apply it and see it in action my visual brain will begin to grasp it.

I don't know if it makes sense, but here's a sincere feedback from a regular C2 user who sucks at math.

The dt guide is very well written, and when you read it, you think(*dt) you understand it. I've read it, I don't know, maybe 50 or 60 times.

But when you have to write tons of events, it would be so nice to have charts you can quickly reference to. Here on the forum, or even better inside C2.

Something like this:

lerp to an angle, use this:

lerp to a position, use this:

lerp to speed, use this:

lerip to scale, use this:

lerp to variable value, use this:

every tick events: don't use if this and this. Use if this and this.

every X second: don't use.

I must sound super lazy to most of you, and I definitely understand this, but for average users it would be a freaking life saver.

Yeah have to agree!

After reading this thread several times, the dt guide a dozen times, and Ashley's latest blog that arose from this thread several times, I now have this fuzzy feeling in my head and a real lack of confidence with both lerp and dt.

All I know is that lerp gives nice smooth movement effect, and that dt is required for a game to be frame rate independant.

But as to how, when, and even if they should be combined, well I would say the general target audience of C2 should just not use it.

Hehe I reckon this is pobably the most confusing thread I have read on these forums.

Really wish I paid more attention to math at school now....

>

> I don't know if it makes sense, but here's a sincere feedback from a regular C2 user who sucks at math.

> The dt guide is very well written, and when you read it, you think(*dt) you understand it. I've read it, I don't know, maybe 50 or 60 times.

> But when you have to write tons of events, it would be so nice to have charts you can quickly reference to. Here on the forum, or even better inside C2.

> Something like this:

>

> lerp to an angle, use this:

> lerp to a position, use this:

> lerp to speed, use this:

> lerip to scale, use this:

> lerp to variable value, use this:

> every tick events: don't use if this and this. Use if this and this.

> every X second: don't use.

>

> I must sound super lazy to most of you, and I definitely understand this, but for average users it would be a freaking life saver.

>

Yeah have to agree!

After reading this thread several times, the dt guide a dozen times, and Ashley's latest blog that arose from this thread several times, I now have this fuzzy feeling in my head and a real lack of confidence with both lerp and dt.

All I know is that lerp gives nice smooth movement effect, and that dt is required for a game to be frame rate independant.

But as to how, when, and even if they should be combined, well I would say the general target audience of C2 should just not use it.

Hehe I reckon this is pobably the most confusing thread I have read on these forums.

Really wish I paid more attention to math at school now....

the smooth movement of lerp comes from an unusual use of it, so indeed it is not easy to think it right, as this use of lerp is already kind of weird (tbh, most people hère I have seen using it just thinks it "looks good, not sure why but I will keep it"), I can understand that ashley gives the "good formula" for people to fix their games, but that does not mean it is a good idea, I would rather see an exponential like interpolation being added.

I would rather see an exponential like interpolation being added.

Yes! I remain perplexed that c2 doesn't contain a native set of tweening functions / behaviour.

But when you have to write tons of events, it would be so nice to have charts you can quickly reference to. Here on the forum, or even better inside C2.

Something like this:

lerp to an angle, use this:

lerp to a position, use this:

lerp to speed, use this:

lerip to scale, use this:

lerp to variable value, use this:

every tick events: don't use if this and this. Use if this and this.

every X second: don't use.

If you're rotating, moving, accelerating or basically anything else, the answer is just add s * dt. "Every X seconds" is already framerate independent because it measures time, not frames, but people often get confused about it so the original delta-time tutorial specifically covers it.

Lerp is kind of a special case so I added it to the tutorial. I think that basically covers everything?

Pretty cool : )

Thanks a lot, Ashley! Very helpful : )

Ashley

[quote:2un1hba2]s * dt

That would like "value + s * dt" right? I just want to be sure without a doubt

If we used say, bullet behaviour or platform behaviour. Do we need to make events to add dt to the behaviour values or are they already incorporated?

Nesteris

[quote:p0fplsk0]s * dt

That would like "value + s * dt" right? I just want to be sure without a doubt

If we used say, bullet behaviour or platform behaviour. Do we need to make events to add dt to the behaviour values or are they already incorporated?

It seems from the updated tutorial that all behaviors already use dt. Except for the physics behavior.