Welcome to the upgraded PCGamingWiki forums and files page. The current Wiki and Forum bridge is not functioning at the moment, therefore your Forum account currently has no password set. Please reset your Forum password via email check to generate a new password. If you have any issues please message Andytizer on Discord.
The Steam and GOG versions of FlatOut are the v1.0 version. This is the v1.1 patch for FlatOut that works with the digital releases of the game: Steam & GOG.
Originally posted by Clya900, the patch was missing 2 files are now included in this download, patch1.bfs, and patch.ini. Without these files, the game would fail to load, and shows a Runtime error. The game now has been tested on the Steam version, and works perfectly fine, however the GOG is untested, but should work just as well.
Original patch notes below:
FlatOut PC patch v1.1
To install the patch:
Copy the Flatout.exe, patch1.bfs and patch.ini files to the root of the install folder (by default this is c:\program files\empire interactive\flatout) and run the game.
The following items have been fixed or improved:
* Fix for the nVidia 66.93 drivers. The game no longer crashes when a race is started. The game has also been tested up to the 67.03 drivers with no problems found.
* Engine fire burns aligned to the car's coordinates, e.g. when the car is upside down, flames go down.
* Tuning menu: BHP meter and colors randomly switch when changing profile.
* Flip back and forth to statistics screen and the BHP grows bug.
* Force feedback slows game in some cases.
* 5.1 sound support is not working on some setups.
* Disconnects when returning to the lobby in multiplayer games.
* When the game briefly minimizes before starting a multiplayer game, sometimes gives a blue screen (this is quite rare, but it does happen sometimes)
* Only 2 players can play if NetLimiter is installed.
* Bug with public ip detection, if the commandline network options are used.
* Enabled a switch to allow the player to turn off ragdoll in single player (located in the Options Menu).
* Enabled multiplayer destruction derby.
Hi, my name's Voxarp. I learned of PCGamingWiki from the late TotalBiscuit's videos back in the day and I used to help contribute from time to time but now days I'm mostly just a user. Thanks to everyone involved for providing such a great wiki!
Recently Valve has introduced a new feature of SteamPlay called Proton which is a variant of WINE that allows Linux and possibly OSX to run Windows-only games. It's an exciting time!
What the community seems to desperately need is a resource to:
Report game compatibility, possibly with a WineDB type rating of Bronze/Silver/Gold/Platinum - right now all we have is a spreadsheet on Google Docs. Present fixes and workarounds for games that don't work out of the box. Provide clear delineation between Proton versions, a game might work properly on one Proton version but not another. Possibly provide an overview page with statistics on the percentage of games working, with a table that lets you sort by criteria such as Proton version or compatibility rating. I know this is a lot of effort and not to be taken lightly, but I feel it fits right in with PCGamingWiki's objective of providing fixes and workarounds for every single PC game.
Valve's Announcement: https://steamcommunity.com/games/221410/announcements/detail/1696055855739350561
SteamPlay on Reddit: https://www.reddit.com/r/SteamPlay
linux_gaming on Reddit: https://www.reddit.com/r/linux_gaming
Compatibility Spreadsheet: https://docs.google.com/spreadsheets/d/1DcZZQ4HL_Ol969UbXJmFG8TzOHNnHoj8Q1f8DIFe8-8
Hey, I was just wondering if it would be possible to add the APIs for VR? These are the current and upcoming PC VR APIs:
OpenVR OSVR (Open Source Virtual Reality) Oculus SDK Windows Mixed Reality (The headsets are technically called Windows Mixed Reality Immersive Headsets) OpenXR It would make sense to have both the APIs and headsets as different sections, as different APIs can be be used for different headsets.
Plus, it would make it easier to differentiate if a game supports Oculus Rift CV1 or just DK1 or just DK2. As Oculus SDKs before 1.3.2 (i think) only worked on the DK1 and DK2.
So perhaps if the SDK version is set to one before that, the Oculus Rift headset section could be changed to reflect that it only supports DK1 and/or 2.
Also, it means there's future proofing for when the OpenXR standard gets released and games start supporting it.
I'm sure this wouldn't be as simple as Im making out, and this is just a suggestion to get it to work, and a possible solution the the DK1 & 2 problem, so I understand if you don't do it or do something different.
Hopefully my suggestion come sin useful :)
Also, could Tobii EyeTracking be added to the to the non-VR, VR support section? There's a fair amount of games that support it now so it might be useful having that there :)
Valve have changed the name of the 'Steam Controller API' to 'Steam Input API'. The wiki still has the old name, could it be updated please? :)
By Fwinest JediThug
Download the ZIP and drag the contents called "link.exe, Manhunt Fix.bat, mspdb80.dll, patchrun.bat" into you're Manhunt folder.
Once the "link.exe, Manhunt Fix.bat, mspdb80.dll, patchrun.bat" is in the Manhunt folder run Manhunt Fix.bat and another command prompt will show up, press enter.
Recently Browsing 0 members
No registered users viewing this page.
Who's Online 1 Member, 0 Anonymous, 32 Guests (See full list)