Startzones, "Lags", and Moving Forward

Interpolation such as in the momentum mod will be not possible unless we remake like ~80%+?? of the zones. Many zones are created by using triggers that are compiled into the maps. If these triggers are perfect rectangles then we can write a vmf analyzer to read the planes of these triggers to generate the dimensions of these triggers.

But even then there still remains a good amount of triggers that are not rectangles, some are spheres, some are triangles, some could be a variety of shapes.

This is not an impossible job, in fact the hardest part of this whole thing would be to remake the triggers manually and reset the times (there should not be THAT many of these). Analyzing all the VMFs would be simple once something is written to do it. (We can tell that its a perfect rectangle by analyzing the coordinates of the planes).

In fact I started on this a year or two ago but I put it on hold because there were more pressing issues to take care of.

A note about interpolation: This is still an approximation of your position/time, but it would be better than the timer lottery (Physics cannot allow us to know the exact values anyways). Timer lottery has always existed to break ties though.

----

Currently in the database the speed is saved as XYZ, I'll change it to save XY and Z separately.

Quote:

---

Originally Posted by Rickzter

When we tested it earlier u could get more than 350 XY and a 334 edge (Z) if u did it perfect. I admit a 334 didnt happend all the time but when you got it you could feel that u did a really good prestrafe, exiting the zone in a perfect 90° angle. People saw me get it 3 times in a row some times. (think it was skandy and morning) when i really tried for the perfect prestrafe. If its assumed to be a "false start" then it just happends WAY too often. Alot of ppl who specced me during testing will confirm.
The "best" i got was 352.xx/334

---

1. On what stage were you testing?
2. Assume that 334 was the maximum possible z speed, as you claim. That means with a 1-tick lag, we would see 340/346 (no-cj/cj) much more frequently. However, these values are exceedingly, exceptionally rare. Moreover, whenever there is a false start of more than 1 tick, it tends to be significantly more than 1 tick -- up to 4, 5, or even more (I believe these lags are actually something entirely different and unrelated because of this). But 340/346s are almost never seen, and in my testing, I can't recall ever actually finding a 340/346. If 334 were the maximum, they would be so much more common than they are now that I think it's reasonable to throw away the 334-max hypothesis.

I plan on doing some more testing tonight, hopefully with timescaling/!speed.

Doesn't !speed change the gravity? I'd go with real timescale.

Quote:

---

Originally Posted by Beetle179

1. On what stage were you testing?
2. Assume that 334 was the maximum possible z speed, as you claim. That means with a 1-tick lag, we would see 340/346 (no-cj/cj) much more frequently. However, these values are exceedingly, exceptionally rare. Moreover, whenever there is a false start of more than 1 tick, it tends to be significantly more than 1 tick -- up to 4, 5, or even more (I believe these lags are actually something entirely different and unrelated because of this). But 340/346s are almost never seen, and in my testing, I can't recall ever actually finding a 340/346. If 334 were the maximum, they would be so much more common than they are now that I think it's reasonable to throw away the 334-max hypothesis.

I plan on doing some more testing tonight, hopefully with timescaling/!speed.

---

I was able to reproduce it in most places. Omnific s1 and commine too beta b1 for example

Quote:

---

Originally Posted by Sacred

Doesn't !speed change the gravity? I'd go with real timescale.

---

!speed changes your tickrate inversely proportional to the speed value (!speed 0.5 would make your effective tickrate 66.6*2=133t)

Quote:

---

Originally Posted by Rickzter

I was able to reproduce it in most places. Omnific s1 and commine too beta b1 for example

---

Can you comment on my second point, how 340s and 346s are obscenely rare, much rarer than we know false starts are?

Quote:

---

Originally Posted by Juxtapo

!speed changes your tickrate inversely proportional to the speed value (!speed 0.5 would make your effective tickrate 66.6*2=133t)

---

This is true and something I hadn't realized until it was pointed out to me before I started testing. I have another idea which I'll be trying pretty soon.

340/346 occured very rarely indeed.

Considering how often 334 occured if u really try idk if it should be considered a "false start"

I was also testing how often i could get -334 z vel, and for me that happened every now and then. But while testing for like 20 minutes, -346 z startzone occured only once, whereas -334 about 10 times. Also, when i normally play a stage/bonus/map and dont focus as much on prestrafing as i did while testing, i feel i get +475 startzones MUCH less often.

This thread seems heavily focused on start zones, when in reality this happens with every single zone. Also it is 100% random on whether or not you leave or enter a zone 'between' ticks. Also I'm not 100% positive it is actually happening because you are 'between' ticks, since there are points where you can be +/-2 ticks in and out of zones. Based on luck you can be 4 ticks faster, since you can leave a start zone 2 ticks late (more time it registers you are in start zone) and enter the end zone 2 ticks early.

It's irrelevant for end zones, you would just enter them late and get a worse time.