United StatesThere is no .swf file and there will never be a .swf file because this is not a flash game. Shockwave games run using .dir/.dcr files made in Adobe Director, distinct from .swf files made with flash creation software.
In other news. I am currently bug testing the game on my TI-83 calculator. Looks like it has the desired 0.005 fps and should clock in at 2 s in-game time. Look forward to the new wr, should only take about a month to complete!
Just to clarify, the file we have on the resources tab contains a macromedia projector file which is a .exe file that can run without needing to install any software. Just download what we have on the resources page, extract the contents of the zipped folder, and click the .exe projector file to launch the game. That should be all you need to do!
This game was actually made to run on adobe shockwave (great at 3d games) which is distinct from the much more common adobe flash. As you can see, people often get the two confused!
So in the hopes of tackling the IGT issue I did my best to investigate the runner.dcr file. I was somewhat successful, and made a few simple modifications to the game:
-Invulnerability -Increased fuel capacity -Items in different locations -All areas loaded at once (allows for a neat shortcut) -New text on end screen
Unfortunately, I was unable to see how the IGT worked at all, so it is likely buried in byte code that is indecipherable for me. Below is a """"speedrun"""" I did on my hacked game to showcase these changes.
Does anyone know the maximum framerate of this game? I assume 60, but can anyone confirm?
As a sidenote, my working theory is that every 1 second IRL is clocked as 1.25 seconds IGT under perfectly lagless conditions. Maybe figuring these things out could be useful for us?
Game speed definitely does depend on many factors. For me there is even a difference if I'm recording or not. I lose about 1 second every 20 seconds RTA to my non recorded splits, which is why my splits are often all red in my runs
Who said TAS was a problem? He doesn't even have world record in this game lel
Would be nice if we could hack the game to display IGT.
Maybe, but I think there is still potential for a consensus resolution here. Also f1 was active today I'm confused when you say the moderator is not active lol.
Goomba do you think that your run should remain on the leaderboards?
My main argument against it being on the leaderboards is that it was sped up in post, with a potentially glitched out shockwave player as well.
I still think IGT is the best bet we have, as explained in an earlier post I wrote in this thread.
He did claim it happened randomly in the discord we made
- "I just started up the game and it was laggy af, so I tried it out"
- "...but my flash lagged for some weird reason for that run"
- "... as for my last run, it randomly lagged I did 1 run with it and well there ya go" https://discord.gg/jg8U8yj
Also @f1 I believe @Goomba was just trying to make a demonstration by submitting his run and was not acting maliciously in any way. Goomba did not slow the game intentionally to get his run, it just happened randomly. Also, Goomba only sped up his run in post in order to show the perceived problems with IGT. I don't think it's right to attack Goomba on this.
One potential course of action is to remove @Goomba 's 3:28.8 time from the leaderboard on the grounds that the video was sped up in post and is not exactly verifiable (also the game itself was possibly glitched on his machine for that run).
IGTs are very close between runners for the most part, and if Goomba had the unsped up original of his 3:28.8, I would view it as a bit more legitimate. I know Goomba expressed some doubt over f1's run (and mine), but f1's double tunnel boost is pretty solid and could be enough for WR since my 3:36.0 had a few awful mistakes but lucky ending RNG and Goomba's 3:36.2 didn't have as quality of boosts and had a poor ending. Lines just really don't matter compared to boosts.
In short, I still don't have compelling reason to doubt IGT, but I do feel that the 3:28.8 should probably be removed, and hopefully we can get Goomba on board as well. That way new runners will be able to compete without feeling like they are trying to beat a sketchy run.
Also @Jumpyluff f1 will always return!
Before we get ahead of ourselves, I do want to point out why IGT is used in the first place. RTA times are wildly different between runners depending on their setups. For instance, my run is about 12(!!!) seconds faster than f1s, 10 seconds faster than yours, and about 8 seconds slower than goomba's, putting an astronomical 20 second gap between f1 and goomba. Let's not kid ourselves that RTA timing is more fair given our current pc setups.
How bout we get in touch with the officine pixel devs and beg them for the raw .dir files from 2004. Either they somehow have them or the game dies. It's a win-win!
So... is there a reasonable solution other than RTA? Seems unlikely, unless goomba's generated lag is somehow different from "normal" lag. If RTA is the only option then goomba has wr by like 10 seconds, and I could hop on a friend's battlestation desktop and bop everyone else in a few minutes. Both IGT and RTA appear to not reflect true skill.
Is there a third option? Some way to count in-game frames (and would that even help anything...)? How much BS is worth sifting through to make this game fair to speedrun. We can't exactly TAS it or easily log our inputs on a frame by frame basis.
This makes me sad mate :( You seem to be correct. What did you use to generate the lag? Pour one out.
Epic run, who knew there was so much time to save?! Tbh I may recall encountering a similar glitch playing as a kid like 8 years ago on miniclip, but that memory might be total bs.
If people actually start running this game seriously we might need to standardize which version of the game people are playing for some degree of consistency. I use the offline file provided in the resources tab, no idea what goomba uses. As far as IGT goes, I won't be able to compete if it is no longer standard because my laptop lags for a cumulative >8 seconds every run (or ~5 sec if not recording).
