Joined: 4/17/2010
Posts: 11673
Location: Lake Chargoggagoggmanchauggagoggchaubunagungamaugg
We accept PCem Windows XP movies for submission now, and in addition to ourguides we also need to have a place for all the discussion about this setup, results of tests and all sorts of useful advises, which we could add to the wiki guide.
Warning: When making decisions, I try to collect as much data as possible before actually deciding. I try to abstract away and see the principles behind real world events and people's opinions. I try to generalize them and turn into something clear and reusable. I hate depending on unpredictable and having to make lottery guesses. Any problem can be solved by systems thinking and acting.
The duration of time it takes for Windows XP to actually finish booting up and take you to the desktop is rather inconsistent between different time-and-dates in libTAS (with half of the outcomes being a full 17 seconds longer!). I've documented the duration and outcome of some of these possible starting times in a spreadsheet here: https://docs.google.com/spreadsheets/d/1_j1zkYPPHR4jLLW3bybvnjsN6K7sV_vWZHLm7X5SwaE
Windows XP in general seems to be rather sensitive and unpredictable with lag. Simply moving the mouse around on screen seems to be able to affect the duration of loading times (often for the worse), and clicking on things the first frame they appear often seems to result in slower loading times than waiting a few frames beforehand. Without a better understanding of exactly what Windows does behind the scenes with managing tasks, the best solution here seems to be one of trial and error. Regarding avoidance of the mouse, I've found a rather comprehensive cheatsheet for keyboard shortcuts that may prove useful to others: http://www.shortcutmania.com/Windows-XP-Keyboard-Shortcuts-printable-cheatsheet.htm
CD loading times in particular seem to present a difficult hazard for TASing, as loading earlier savestates after PCem has started reading from the CD image seems to cause desyncs, and even strange errors from XP itself on some occasions:
Running the movie from the very start seems to give consistent timings without errors, but combined with XP's strange lag inconsistencies, it seems game installation in particular is likely to be a pain to optimise.
The duration of time it takes for Windows XP to actually finish booting up and take you to the desktop is rather inconsistent between different time-and-dates in libTAS (with half of the outcomes being a full 17 seconds longer!). I've documented the duration and outcome of some of these possible starting times in a spreadsheet here: https://docs.google.com/spreadsheets/d/1_j1zkYPPHR4jLLW3bybvnjsN6K7sV_vWZHLm7X5SwaE
Wow—super interesting! Just looking at the "Res increase" column, it seems to oscillate between 44.4 s and 53.42 s about every 10 years. (The difference between adjacent rows is 100000000 s, or about 3.17 years.)
I wonder if the dynamics are as simple as: there are particular timestamps at which the time required to boot suddenly changes. For example, timestamp 1300000000 yields 44.4 s and timestamp 1400000000 yields 53.42 s: would a binary search find a pair of consecutive timestamps where one is 44.4 s and the other is 53.42 s?
The duration of time it takes for Windows XP to actually finish booting up and take you to the desktop is rather inconsistent between different time-and-dates in libTAS (with half of the outcomes being a full 17 seconds longer!). I've documented the duration and outcome of some of these possible starting times in a spreadsheet here: https://docs.google.com/spreadsheets/d/1_j1zkYPPHR4jLLW3bybvnjsN6K7sV_vWZHLm7X5SwaE
Every "long" load occurs during daylight savings time, and every "short" load occurs outside of it. I wonder if that's relevant.
Joined: 4/17/2010
Posts: 11673
Location: Lake Chargoggagoggmanchauggagoggchaubunagungamaugg
Oh god so it makes a difference in the end D:
Warning: When making decisions, I try to collect as much data as possible before actually deciding. I try to abstract away and see the principles behind real world events and people's opinions. I try to generalize them and turn into something clear and reusable. I hate depending on unpredictable and having to make lottery guesses. Any problem can be solved by systems thinking and acting.
Well, I did a little bit of testing from the v2 verification movie before this, and the same starting times were longer there. So I suspect that either the removal of daylight savings doesn't actually get saved due to restarting during OOBE, or that it just takes longer during DST anyways for some reason.
Joined: 4/17/2010
Posts: 11673
Location: Lake Chargoggagoggmanchauggagoggchaubunagungamaugg
InputEvelution wrote:
CD loading times in particular seem to present a difficult hazard for TASing, as loading earlier savestates after PCem has started reading from the CD image seems to cause desyncs, and even strange errors from XP itself on some occasions:
Running the movie from the very start seems to give consistent timings without errors, but combined with XP's strange lag inconsistencies, it seems game installation in particular is likely to be a pain to optimise.
I think this proves that game installation deserves to be in a separate movie if a CD is used. Do you know if floppy disk installation has the same problem?
Warning: When making decisions, I try to collect as much data as possible before actually deciding. I try to abstract away and see the principles behind real world events and people's opinions. I try to generalize them and turn into something clear and reusable. I hate depending on unpredictable and having to make lottery guesses. Any problem can be solved by systems thinking and acting.
I think this proves that game installation deserves to be in a separate movie if a CD is used. Do you know if floppy disk installation has the same problem?
I don't, unfortunately. I'm not even sure if I currently have a working floppy disk reader...
Warning: When making decisions, I try to collect as much data as possible before actually deciding. I try to abstract away and see the principles behind real world events and people's opinions. I try to generalize them and turn into something clear and reusable. I hate depending on unpredictable and having to make lottery guesses. Any problem can be solved by systems thinking and acting.
Warning: When making decisions, I try to collect as much data as possible before actually deciding. I try to abstract away and see the principles behind real world events and people's opinions. I try to generalize them and turn into something clear and reusable. I hate depending on unpredictable and having to make lottery guesses. Any problem can be solved by systems thinking and acting.
For some directx 8 and 9 games, it can be useful to use a wrapper to render in software, because directx 8 and 9 are too modern for the Voodoo 3 which is currently the best graphics card emulated in PCem. Some games can look wrong or not even start in hardware rendering, but with software rendering it can be fine. Be aware that it's very heavy on the emulated cpu.
With Pixomatic in Windows XP, after upgrading to directx 8.1 I'm able to play Hamsterball. The main menu still has a black picture but without the wrapper many polygons would be black and textures would have no transparency.
I was also able to play Hotline Miami in Windows XP, with a different version of Pixomatic, but the game seems to be too slow for the emulated cpu with software rendering. It's also a Directx 8 game.
You just take dlls and files from the shader directory and put them in the same directory as your game executable.
For Hamsterball I used Pixomatic version 2 from here https://www.vogonsdrivers.com/wrappers/files/Unsorted/rast.7z
For Hotline Miami I used Pixomatic version 2 from here https://www.vogonsdrivers.com/wrappers/files/Direct3D/Software/Pixomatic/pixomatic_softogl.7z
There's also an opengl wrapper in the zip.
For other games, SwiftShader version 2 may work better but I didn't find good examples. There's a version of SwiftShader version 2 in the first link.
Here's another version of SwiftShader 2 https://www.vogonsdrivers.com/wrappers/files/Direct3D/Software/SwiftShader/SwiftShader%202.x/
There are other versions of SwiftShader so if you're interested you can search for them. People compiled versions to run in Reactos so you can try them as well.
Joined: 4/17/2010
Posts: 11673
Location: Lake Chargoggagoggmanchauggagoggchaubunagungamaugg
Amazing find!!!
Warning: When making decisions, I try to collect as much data as possible before actually deciding. I try to abstract away and see the principles behind real world events and people's opinions. I try to generalize them and turn into something clear and reusable. I hate depending on unpredictable and having to make lottery guesses. Any problem can be solved by systems thinking and acting.
For some reason, PCem only seems to respond to mouse inputs from the player every second frame. (e.g. mouse button inputs won't be registered if performed on odd-numbered frames, and mouse movement will only be detected if it carries over to an even-numbered frame). At PCem's default framerate, this equates to a mouse input rate of 50Hz, while keyboard inputs can be performed at 100Hz. If PCem st-2 is emulated at say, 200fps, then the mouse input rate will instead be 100Hz. It may be best to run PCem at at least double the framerate of your game (or otherwise wait for a fix) if you're planning on making a TAS.
I notice that Abe on Windows 95 has audio issues. I.e: it sturggles to play high pitched sounds inclduing the Windows 95 jingle at it's full capacity.
Here's a video of AE on Windows 95 I did yesterday, the secret chime is making lots of background noise related to audio emulation - I will make an audio only video later.
https://youtu.be/mA4-byY5aHE?si=N4c-FuVNMbwwulr-&t=109
Enjoys speedrunning, playing and TASing Oddworld games!
Has TASed:
Oddworld: Abe's Oddysee in 12.06.13 (with Dooty)
Oddworld: Adventures II in 20.03.78 (with Dooty)
Oddworld: Abe's Exoddus 100% in 2:08:28.4 (with Dooty)
Oddworld: Abe's Oddysee 100% in 1:05:01.65
Oddworld: Abe's Exoddus in 37:18
Oddworld: Abe's Exoddus in 37:15
Oddworld: Abe's Exoddus 100% in 2:!5.44.12
Oddworld: Abe's Oddysee any% in 13:01.3
Oddworld: Abe's Oddysee any% in 12:59.95
Oddworld: Abe's Oddysee 100% in 1:04:16.27
Oddworld: Abe's Oddysee 100% in 1:04:01.07
Currently working on:
Waiting for Windows TAS Tools to work so I can TAS PC version of Exoddus.
Joined: 10/12/2011
Posts: 6533
Location: The land down under.
chuky wrote:
I was also able to play Hotline Miami in Windows XP, with a different version of Pixomatic, but the game seems to be too slow for the emulated cpu with software rendering. It's also a Directx 8 game.
fwiw, Hotline Miami is a Native Linux game that can run in libTAS.
WebNations/Sabih wrote:
+fsvgm777 never censoring anything.
Disables Comments and Ratings for the YouTube account.Something better for yourself and also others.
Last I know, Hotline Miami didn't play nice with libTAS at all, though, since it's a Qt title. If I recall, it has been noted that the rendering thread is not the main thread and is generally unstable.
Enjoys speedrunning, playing and TASing Oddworld games!
Has TASed:
Oddworld: Abe's Oddysee in 12.06.13 (with Dooty)
Oddworld: Adventures II in 20.03.78 (with Dooty)
Oddworld: Abe's Exoddus 100% in 2:08:28.4 (with Dooty)
Oddworld: Abe's Oddysee 100% in 1:05:01.65
Oddworld: Abe's Exoddus in 37:18
Oddworld: Abe's Exoddus in 37:15
Oddworld: Abe's Exoddus 100% in 2:!5.44.12
Oddworld: Abe's Oddysee any% in 13:01.3
Oddworld: Abe's Oddysee any% in 12:59.95
Oddworld: Abe's Oddysee 100% in 1:04:16.27
Oddworld: Abe's Oddysee 100% in 1:04:01.07
Currently working on:
Waiting for Windows TAS Tools to work so I can TAS PC version of Exoddus.
Installation of Windows 98 seems to be impossible without the license key, so we can't support if officially on the site. We support XP and 95 because there's a way to not enter any license key for them.
So you'll have to TAS this game in either XP or 95, depending on which one has fewer audio/visual bugs.
Question tho: did you try enabling compatibility with earlier windows in file properties of the game's executable?
Warning: When making decisions, I try to collect as much data as possible before actually deciding. I try to abstract away and see the principles behind real world events and people's opinions. I try to generalize them and turn into something clear and reusable. I hate depending on unpredictable and having to make lottery guesses. Any problem can be solved by systems thinking and acting.
Installation of Windows 98 seems to be impossible without the license key, so we can't support if officially on the site. We support XP and 95 because there's a way to not enter any license key for them.
So you'll have to TAS this game in either XP or 95, depending on which one has fewer audio/visual bugs.
Question tho: did you try enabling compatibility with earlier windows in file properties of the game's executable?
Enjoys speedrunning, playing and TASing Oddworld games!
Has TASed:
Oddworld: Abe's Oddysee in 12.06.13 (with Dooty)
Oddworld: Adventures II in 20.03.78 (with Dooty)
Oddworld: Abe's Exoddus 100% in 2:08:28.4 (with Dooty)
Oddworld: Abe's Oddysee 100% in 1:05:01.65
Oddworld: Abe's Exoddus in 37:18
Oddworld: Abe's Exoddus in 37:15
Oddworld: Abe's Exoddus 100% in 2:!5.44.12
Oddworld: Abe's Oddysee any% in 13:01.3
Oddworld: Abe's Oddysee any% in 12:59.95
Oddworld: Abe's Oddysee 100% in 1:04:16.27
Oddworld: Abe's Oddysee 100% in 1:04:01.07
Currently working on:
Waiting for Windows TAS Tools to work so I can TAS PC version of Exoddus.
Running the movie from the very start seems to give consistent timings without errors, but combined with XP's strange lag inconsistencies, it seems game installation in particular is likely to be a pain to optimise.
I was also able to play Hotline Miami in Windows XP, with a different version of Pixomatic, but the game seems to be too slow for the emulated cpu with software rendering. It's also a Directx 8 game.
You just take dlls and files from the shader directory and put them in the same directory as your game executable.
For Hamsterball I used Pixomatic version 2 from here https://www.vogonsdrivers.com/wrappers/files/Unsorted/rast.7z
For Hotline Miami I used Pixomatic version 2 from here https://www.vogonsdrivers.com/wrappers/files/Direct3D/Software/Pixomatic/pixomatic_softogl.7z
There's also an opengl wrapper in the zip.
For other games, SwiftShader version 2 may work better but I didn't find good examples. There's a version of SwiftShader version 2 in the first link.
Here's another version of SwiftShader 2 https://www.vogonsdrivers.com/wrappers/files/Direct3D/Software/SwiftShader/SwiftShader%202.x/
There are other versions of SwiftShader so if you're interested you can search for them. People compiled versions to run in Reactos so you can try them as well.
