You shouldn't have problems with OBS really, my suggestion is to capture the game via Window Capture although you'll need to use Silent Patch in order to achieve this (This is located in the resources section)
Probably going to be hard for anyone to do a run of the PS3 version as it was delisted in 2013 so getting hold of it is hard as hell unless you've got a CFW PS3 :/
Yeah I don't see why not, it'd go on the PlayStation section of the game so that's fine.
Might be worth looking at these forums to show how to set up DuckStation to represent Standard Disk Speeds (SDS) and Fast Disk Speeds (FDS)
Standard Disk Speeds: https://www.speedrun.com/mgs1/thread/2u4je/2#boy7m Fast Disk Speeds (FDS): https://www.speedrun.com/mgs1/thread/2u4je/2#tt3qi
Seems like some of that information isn't as accurate as I thought it was a few days ago, upon further testing in practice on both PAL and NTSC regions I found that the shortcuts opened on different laps when you restart the race each time. So it really is randomised for the Interactive races and basically best reaction times will win here.
So recently after doing some testing with DuckStation and finding settings which are as accurate as I can get them to XEBRA here are the settings which should be set for a emulator run using DuckStation:
Console Settings:
- CPU Clock Speed Control Disabled.
- Read Speedup: None (Double Speed)
- Use Read Thread (Asynchronous) Unchecked
Emulation Settings:
- Runahead: Disabled
- Emulation Speed: 100% [60 FPS (NTSC) / 50FPS (PAL)]
Display Settings:
- Show OSD Messages Checked (if a savestate is used, we'll know)
- VSync Unchecked
Enhancement Settings:
- Force NTSC Timings (60hz-on-PAL) Unchecked (PAL speed should be PAL speed and not adjusted by the emulator)
You can check the current date of your version via the General Settings in the Automatic Updater section (2021-01-11), and then post that in your description.
So recently after doing some testing with DuckStation and finding settings which are as accurate as I can get them to XEBRA here are the settings which should be set for a emulator run using DuckStation:
Console Settings:
- CPU Clock Speed Control Disabled.
- Read Speedup: None (Double Speed)
- Use Read Thread (Asynchronous) Unchecked
Emulation Settings:
- Runahead: Disabled
- Emulation Speed: 100% [60 FPS (NTSC) / 50FPS (PAL)]
Display Settings:
- Show OSD Messages Checked (if a savestate is used, we'll know)
- VSync Unchecked
Enhancement Settings:
- Force NTSC Timings (60hz-on-PAL) Unchecked (PAL speed should be PAL speed and not adjusted by the emulator)
You can check the current date of your version via the General Settings in the Automatic Updater section (2021-01-11), and then post that in your description.
Hi there, So recently a lot of games have either allowed or disallowed this emulator since it came on the scene. I know that both MGS and Driver use the same settings to make it as accurate as possible.
Would it be possible to use the same settings for this game?
MGS Settings for DuckStation: https://www.speedrun.com/mgs1/thread/2u4je/2#boy7m
Some things worth mentioning:
- Due to the extra 5 frames per second that NTSC gets, it makes it only slightly faster than PAL but not by much.
- Japanese version is about the same as NTSC but no idea if it is faster than NTSC (My guess it's the same because it's NTSC-J but who knows)
I've noticed some interesting things in the interactive races between PAL and NTSC which can save or lose time depending on which region you are using:
- Stuttgart (Uses slightly different routes for each lap but nothing out of the ordinary here)
- USA (Bridge opens on Lap 3/4 on PAL but on NTSC it is open on Lap 2/3 instead)
- Alpine (Gate on long route opens on Lap 3/4 for both versions and the big shortcut which is the gate near the chicane opens on Lap 4 only)
- Japan (Opens on Lap 1/2 for NTSC but only opens on Lap 1/3 for PAL and the big shortcut near the start opens on Lap 3 on PAL whereas on NTSC it opens on Lap 4)
Stuttgart and Alpine are around the same time on both regions but you lose time on PAL for USA and gain it on Japan whereas NTSC is the other way around.
@GeorgeMHall I'll say yes for now and no for main game categories such as the story (aka Any%)
@GeorgeMHall I've never seen that before and couldn't recommend a fix for it either. How are you running the game? Are you just running it normally or running it in admin mode?
Ok the WRC Challenge category has now been created, get cracking! @Saturn185 ;)
If it's 4 rallies then I'd say all 4 are going to need to be completed in order for the run to be complete
From the sounds of it that sounds like beat a season as fast as possible (This wouldn't be too hard as you could keep entering events and then retiring from them in order for the season to be completed faster) which wouldn't exactly be a long category if I'm honest although this sounds pointless to me as there's no challenge to it whatsoever :/
I'm also puzzled by this turn around, can anyone care to explain why this was overruled and what was the reason? As far as I can see the guy cheated and owned up and got banned as a result but to see it overturned for what was essentially a ban that couldn't really be overturned is ridiculous.
Hi, So as some of you may see now we have a Time Without Loads section for runs, I should just say for the record: THIS SECTION IS FOR THE PC VERSION.
The reason for this is due to a difference in load times between some of us (Most notably between M0mdeck and the other runners with myself being one of them)
We have tried to fix the game on their end and nothing seems to work to give the same speeds as the rest of the runners (And Vice Versa) therefore to keep things as even as possible and to keep things equal we have decided to include Time Without Loads.
If you have any further queries regarding this change, feel free to put them down below.
Yeah for my run I had the game run in full screen when I used to run it on Windows 7 and OBS could capture the separate in-game window so I had to have both the menu and in-game windows constantly showing but when I upgraded to W10 a weird thing happened which was that whenever I wanted to try and capture the in-game window it was like the computer had the mouse click constantly on so I just used Display Capture instead which makes it loads easier.
As for using the better framerate, unfortunately if you did a run with a framerate higher than 60 then that wouldn't be allowed (As far as I know you'd be the only person to run with framerate higher than 60FPS) so sorry about that.
It's weird how people have some problems with this game and others don't, really wish there was a proper fix for this but doubt there ever will be lol XD