Lthats wrong
KI'm not sure if I'm counting the right thing tho
Manglo saxon derived languages
Minteresting
Mwait
Mi know why
Lthat makes sense
Cso your render time is like 1.5-2.5ms
Lyup
Myeah
Mthe timer sucks
Muh i mean the timer's great
Lthe timer is fine, its just not taking frame time into account
Mbut it's implemented incorrectly
Lits implemented correctly, its just being misused
Cso just time the amount of time that's already been done this frame, and subtract that from the timer sleep time
Mmhm
C(make sure to accommodate for when the current frame is already longer than the target sleep time)
Mcan't sleep for a negative amount of time
Cpretty sure it's either infinite or zero time
Lnot with that attitude
Acomputers can't
i however can
i however can
Cwindows waitable timers i think interpret negative values as relative, and positive as a specific date, and I'm pretty sure (at least i hope so) that breakneck timer uses the relative by default
Llook at ze code
C
Ci wish i could
Mfgvdfjghf
Lhave you heard of a Web Browser
Mther3e's a github app
Ayes
Lyes
Ait is terrible
Csounds like a lot of work
Mi wouldn't know i don't use phones
Cit's about average
Lthe share button literally lets you forward it to a web browser
Ci was too lazy
Lskill issue
Mforward it to your mother
Mshe loves coding
Cyikes
Lso real
Canyways
Acan't forward it if you don't have one smh
Mtrue
KHmm... would I get an accurate reading of how much time is spent on my messy code if I used a stopwatch to measure around
window.DoUpdatewindow.DoRender()Or is that a terrible idea for accuracy?
Myeah it's alright
Mstopwatch is HPT it'll work
L(not on all platforms)