Messages

In other news, I stupidly crashed an even better lap in the high curve. 

You cannot view this attachment.

There will always be ways to cheat. The only thing I did was make it an effort to do so.

The reason I mentioned save states is because they are available in several versions of DOSBox and it takes little to no effort to use them.  It's a matter of transparency, similar to telling someone that you can use traditional replay handling in Stunts when they weren't already aware that was possible.

If transparency is the point, why didn't you inform the community before the race started?

Now we are eight already!  It would be cool if pipsqueaks who don't have the time for a whole month of Zakstunts at the moment would give it a lap. @Akoss Poo a.k.a. Zorromeister, @CTG perhaps?

On another note, the competition should be cross referenced better. I suggest adding it to the portal at least.

Happy racing!

@Daniel3D, I noticed the site is very similar to CCC, where @alanrotoi is admin. Couldn't you make him admin on the NoRH site also, to take some work off your shoulders?

I probably messed up something - for me fast-forwarding is producing the same result as playing.. :-/

Playing with this bug is very dependable on the setup used. So, don't be dismayed if you can't reproduce the anomaly...

Maybe or maybe not. @Friker: If you post a gif of what you did, I can tell if you made a "mistake". I also agree that 1) together with 2) are currently our best bet. That way, we would be able to verify most but not all replays.

At the risk of stating the obvious, let me elaborate a bit on what I found (using my system). After frame 1.46.00, the car in Friker's replay is following 3 different paths simultaneously. By using the replay controls, you can access and drive each path separately. For example:

- If you finish path 1 (the one that currently crashes into the bridge), the car reaches the finishing line when you click the replay button, but Duplode's method fails.
- If you finish path 2, the replay button crashes the car, but Duplode's method works.
- If you finish path 3, both the replay button and Duplode's method are not suitable to verify the replay. 
- To fix the replay, you have to start driving a bit before 1:46:00 and the anomaly will likely vanish.


I hope that made sense! 

Ok, here is more research. Please note that I am not doing this to prove Duplode's method is bad, but to gain a better understanding of how the engine works. 

I have created a replay that shows a crash both with the play button and Duplode's method. However, I actually finished the lap, please see the gif below. The replay is also attached.
If I can do this on purpose, it can also happen by accident when using replay handling.

You cannot view this attachment.

You cannot view this attachment.

Edit: Another relevant question is whether there are replays that show as a crash with Duplode's method but play correctly when using the play button. I did not test it but think that is the case.

I made a GIF for @Friker. Here it is: (Ending 3)

EdIt: It is quite slow so you have to wait a bit before it starts. Sorry!

You cannot view this attachment.

What is your time @Erik Barros?

I wonder how many pipsqueaks are going to participate. I know @alanrotoi and @Duplode will, perhaps @Overdrijf and @KyLiE.   Anybody else?

Ok, I did another experiment, and it gets even worse. I managed to create a replay in which the car finishes with two different finishing times! The evaluation screen occurs in both cases. 

Here is how you find them:

1) Pressing "play" from the beginning causes a crash on the bridge.
2) Using the Duplode method (Load from Options, go to the end of the replay) shows the car finishes in 1.57.95 plus 9 seconds penalty time.
3) Go to frame 1:46:00, press the 0.05 forward button until frame 1:48:00, and press play. The car finishes in 2:20:00 without penalty time.

Comments:
- The methods described in 1-3 are sufficient but not necessary to produce the different endings. There are other ways to produce them, in particular Ending 3).
- Ending 3), which cannot be confirmed with Duplode's, method is slower than ending 2, which can be confirmed with his method. However, I can produce a replay in which Ending 3) is faster than Ending 2).
- Duplode's method may still be better than the status quo. In particular because, according to @Frieshansen's research, it can happen that a replay crashes on the manager's but not the pipsqueak's computer when using the play button. I find that unacceptable. I am hoping we are able to find a better method though.   

You cannot view this attachment.

This is the end of the third Friker.

You cannot view this attachment.

Wow, I have missed a lot of posts while I was away. Without further ado, here is some more research:

I found that the problematic frame in Friker's replay is 1.46.00, in which the car completes the sharp turn. All pictures below are generated from the same replay:

Picture 1: Press play button from 1.46.00 or before
Picture 2: Load the replay from options / Press the play button or the 0.05 forward button from 1.46.05 or later
Picture 3: Press the 0.05 forward button from 1.46.00 or before
You cannot view this attachment.You cannot view this attachment.You cannot view this attachment.   

So there are actually 3 different states 

So, I guess the meeting is off? This is a pity as I was looking forward to some in-person live racing!

An alternative to skipping it entirely would be running a scaled down version on a random weekend, where pipsqueaks arrive on Friday evening and leave on Sunday morning. Of course, this version may not be too attractive for those of us with significant travel costs. On the plus side a meeting is probably easier to arrange if we aren't too ambitious. Thoughts? 

Do you like it @Cas  ?

Here comes this month's teaser. (It is probably as useful as the MCLaren one from January  )

 

For me it was the case. When reaching 13:58 the game forced me not to drive anymore. Anyways, do you race with full speed? I used UNZ to test it

Yes, I am using fast simulation speed and the emulator Tsugaru.