Wielkopolskie, PolandThat's also something I noticed in lots of people's videos and what always kept me wondering what's wrong with their configuration, because I don't remember ever experiencing it, at least not regularly.
I think it's not a good idea to assume this happens consistently regardless of the hardware and software configuration. That factor must be taken into consideration.
Most of people seem to be running on Windows 10 + ??? hardware, which means that we need a bigger sample of players running on other operating systems, including Linux and Mac if possible.
As for myself, I run Windows 8.1 x64 Basic Edition on an Asus X555LJ notebook and don't experience the same issue (see my videos). Additionally, I run the game using the Glide renderer, through nGlide software wrapper.
These things might be all very important, because if one mode behaves consistently differently, we might need to enforce that everyone uses the same config.
As I probably said earlier, I have no strong opinion on this. While I wouldn't do it myself, I don't really think it should be explicitly banned either.
Still though, I think this kind of strategy is better fit for 100% Completion category.
Bottom line, this is a neutral vote from me.
If there's no explicit mention of something specific in the rules, it should be assumed that it doesn't matter. I don't think we should tell people whether to run the game in window or fullscreen as long as they don't do stupid things, like enabling extended DxWnd hooks that make it possible to alter in-game time by affecting the game loop timing.
Same with StuntKit modules, though as far as I'm concerned I'd prefer the game to be ran with as little support of external tools as possible (minimal setup that makes it comfortably playable, to minimise the possibility of the game being affected by external bugs/weirdness of 3rd party software)
Choice of speedrun time measuring tools is open to the preference of the runner. I don't think many game moderation teams on SRC enforce specific timers, am i wrong? Using the autosplitter is preferred but as long as there's no millisecond differences, it won't matter whether you start/stop manually or not.
As for old records, I'm not really in the favour of "rewriting history" and just deleting them. The save category split was made for a reason, and i fail to see how it's supposedly a bad idea, since people are free to run whatever category they prefer.
I think we need more people to say something on the subject matter first so it can be decided more democratically. As far as i'm concerned, for now i'm not really convinced so my vote is no. Hopefully others will have something to add.
Trust me, I thought about it because in-game timing would have been ideal (it's great in another game I run, Thief 2), except it introduces more mess than anything when it can't be easily applied to all categories.
Ideally both arcade and championship would sum up the entire time spent on racing track and display it after completing the game so you could just use that and deem it the official speedrun time measuring method. Although that's sadly not the case and manually summing up all championship times would be an impractical chore.
So even if that's way more viable for Arcade I'd rather avoid doing that just to keep one, consistent method of dealing with time.
I was initially rather indifferent about that one, as long as the player makes it to the final finish line, but now I'm leaning to agree with it. Let's wait a bit, maybe others would want to say something on the matter too
Hmmm... That's strange, I don't think I know what the issue there is, but if you're on the notebook computer, or a computer with multiple GPUs in general, make sure everything uses the same GPU (if you don't know how to check it, there's an official troubleshooting guide for notebooks https://obsproject.com/wiki/Laptop-Troubleshooting)
As for what settings I use, I'm not at the computer at the moment but I'll try to describe it from memory as accurately as I can. First off, I'm running the last version of old OBS Classic rather than Studio. I ensure everything runs on the same GPU. Stunt GP is sourced from game capture, timer (WSplit) is sourced from window capture. In OBS settings, video framerate is set to 60FPS, at 1366x768 resolution, bitrate is 9000Kbps, 320Kbps for audio. On the advanced tab, encoding profile is set to superfast and CRF set to 10. One last thing that might or might not make a difference for you, I run SGP in 3Dfx Glide mode rather than DirectX. I use a wrapper called nGlide (it's freeware) to make it work. I need it on Windows 8.1 because DirectX 6 mode isn't hardware accelerated and runs badly. I hope this helped in any way.
This sounds like a very specific issue, but I'm not sure if I'm understanding correctly. Did you use Game Capture source to record LiveSplit? It should be Window Capture instead. Game Capture should be used for SGP (it's intended for programs that display things via DirectX or OpenGL)
Btw, I'm not a boy :)
Hey, welcome, always nice to see another person interested in this game!
You asked about many things, so going one by one:
- The savestate rule means that before speedruning the game you need go to the options menu and use the progress reset function first (whose English name I don't know, since I only own Polish version. You'll find it, it's impossible to mistake for anything else). Sadly, the game doesn't provide any way to backup the save so you need to do it manually from the OS' file explorer before resetting it in the game. You'll find the directory containing the save data in the game's root folder, simply zip it and store somewhere and you're all set
-As for the second issue, I'm taking a wild guess you're new to speedrun in general, as this isn't a SGP-specific problem. You'll find general video capture and timer usage guides all over the internet. To keep it short here, you'll need an external program like LiveSplit to measure and display the time. As for recording, I recommend OBS, either modern OBS Studio or OBS Classic if your computer is really slow. My average file size of a ~15min run at 1366x768px and 60FPS takes about 1.6GB but you can shave more space taken by it by halving the framerate for example.
BTW, your English is perfectly comprehensible, don't worry. And most importantly have fun!
Why exactly are you holding the info on how to perform the duplication back, rather than just sharing it? It's an interesting bug.
BTW, I think this probably should be disallowed for 100% runs if it makes it possible to overflow the counter.
Yeah, I'm gonna make the clean save for Arcade a requirement from now on, if anyone has any objections to it, please do say so. I really don't want to act retroactively though and won't invalidate existing runs if they don't have too much of advantage (i.e. could still be beaten on fresh save).
I'm all for the idea of Championship being divided into 2 subcategories, Clean Save and Any Progress Level. This way we won't have to invalidate anything that's already there on the leaderboard.
As for the TT, i need to watch what happens in the 100% runs, but if i were to decide, the requirement would be to achieve an "outstanding lap" on every TT track. And yes, presenting the catalogue menu after the timer had been stopped is very much encouraged!
PS. friendly reminder, than in case of objections, suggestions or comments, please chip in to the conversation @everyone
As we all know, for the longest time there weren't any actual rules posted regarding running SGP, so I want to remedy it by finally filling the gap with something unambiguous and concise. I already revised some basic rules regarding the correct method of time measurement in Arcade and Championship modes.
There's much more to it though, and there's some nuances that Halamix drew my attention to, yet it is something i can't and don't want to decide about on my own, as there needs to be some community consensus.
First, the savestate problem. Halamix noticed that my Arcade runs lack the "Track xxx unlocked" screens between races, caused by the fact i had already unlocked them before and i'm replaying Arcade on the same savestate without resetting it prior to each run attempt.
This raised a question, whether or not it should be enforced that the players start each run with their savestates cleared beforehand so all of these screens would appear. It's probably negligible in terms of the amount of time saved, but i'd rather make this a rule.
Second issue, indirectly related, also involving savestates. In their Championship WR run, Pikoczek drives the Team Machine throughout the most part of the game, which only becomes available after obtaining the access to it in Time Trial mode. People who play on a fresh save wouldn't have such an opportunity, therefore this is subject to further discussion whether or not it should be allowed.
Third of my concerns, and last one for the time being, pertains to the 100% category. What does it mean to "complete Time Trial"? When is it considered completed? After doing a single lap on every track? After beating some specific time? Something else? I need a clarification on this.
Since this is too important to decide about on my own, i ask everyone interested to voice their opinons and discuss it.
Late to reply to this, but seems that the moderation issue is resolved now, since Halamix and me were admitted as additional moderators. From what I'm aware of IceBlock had lost interest.
I still stand by my initial idea of starting the timer immediately after the game mode has been picked (that would be only relevant to Championship and Arcade) and stopping it at the finish line of the last race (adhering to the general canonical speedrunning rule of "last meaningful input")
As for the 100% category, we could probably start counting right after advancing past the title logo screen and stopping it in the moment of completion of all the requirements
I have no idea what we'd do with runs that break those rules though... probably officially invalidate them? IDK
I'm open to thoughts of anyone who's interested
Can't speak for everyone, but i think it's perfectly fine to only have the leaderboard for unmodified game. Speedrunning mods is a controversial topic imo and there might be substantial differences between subsequent versions of specific mods, leading to unfair discrepancies and advantages/disadvantages between players (unless it's succesfully enforced that everyone uses the same version)
It's interesting there are literally no PSX1 version runs, i might try and give it a go, since it's the only one i own
Funghi for life. Spinach, chicken and tuna or shrimps are also great on pizza. Garlic or basil are welcome. Salami occasionally.
I don't have any strong opinions on pineapple on pizza, though I'm not really a fan of sweet pizzas. Just don't put too much onion or cucumbers on it. I cannot suffer cucumbers
Difficult to decide between Clefairy and Furret (both are cute, that's the reason). I remember having Furret as my team leader in Gold (2nd generation) and leveling it to around lvl 70
HowDenKing, I have the exact same Logitech K280e and while it's not gaming oriented I really like it. Ghosting is minimal and you need to be playing or doing really specific things for it to drop any input. Other than that, no idea why you think it's that bad.
Honestly, what bothers me, is why people who are seemingly at least moderately tech-savvy (I guess every speedrunner) don't all like the idea of using a password manager like Keepass.
