Here is me and few guys from Fastest Sector. Wheel paddles are behaving weird, I definetly need to tweak them.
http://www.youtube.com/watch?v=ymYsR8TmGhQ
http://www.youtube.com/watch?v=ymYsR8TmGhQ
-
Hey, guest user. Hope you're enjoying NeoGAF! Have you considered registering for an account? Come join us and add your take to the daily discourse.
F1 2012 |OT| 2011 + 1
- Thread starter Foliorum Viridum
- Start date
There's no mention at all of a fix to the handling, but I have to admit that it's impressive Codies have rolled out those fixes so quickly. Beats me why they didn't know about them now though, given it's only taken a week for the public to discover each and every one of those known bugs.
Edit: Just saw the "200 bugs and fixes". How the fuck can you release a game where in the space of a week, your customers can find OVER 200 BUGS?!? Fucking pathetic. Hopefully they have a list so we can see just how inept they were during "testing".
TJP
Member
Why do you think I highlighted that passage 8)
Yeah, I figured as much! But I just saw "patch" and quickly went to the list. I'm guessing that not included in that list are the 180 things they're too ashamed of that they fucked up.
Hopefully someone will be clued up enough to compare the game's files pre and post-patch to see what they did. Given it's all in XML format, it shouldn't be hard.
But I'm glad it seems they're on the ropes, though. Despite maintaining an Iraqi information minister-esque facade, it looks like they're actually doing work behind the scenes. I suppose they have to... if they screw this one up (on top of last year's patching problems) then they'll lose way more customers than they can afford.
PC, XB or PS3? If PC (or Fanatec on XB), you should profile G25 (or any other wheel) into the 320/330 degree mode and kill both Sensitivity and Linearity in in-game options to 0. You will get perfect 1:1 Linearity, I was talking about it on my post related to wheels on the previous page.
If on PS3 or MS wheel on XB, then no luck, majority of people on Codemasters forums are rising awareness of 320/330-degrees being a perfect point for profiling a 900-wheels (instead of defaulted 270). However, there is some consensus regarding settings for Linearity and Sensitivity that best mimics 330-degree steering:
Deadzone - 0%, Steering Saturation – 10%, Steering Linearity – 75%. I hope it will help you.
I am so amazed about how many actual wheels F1 2012 is supporting but I am also amazed how actual 1:1 steering does not work for any of them out of the box. I presume it would be a great step forward in programming if they would bypass the usual 900-degree SDK routines for console API's and just made 320-300 degree as default-value for steering during wheel calibration instead of default 270. But I am probably overthinking it.
To be honest, I presume it has actually nothing to do with "customers" finding anything, but with releasing a patches that they've been working on since final testing phase, after the Gold has been submitted to factoring.
This is too early to take into account any "customers" bugs, those are probably bugs and details that couldn't be ironed out prior to game release which they were already aware of - but they couldn't postpone the release.
"Customers" bugs database is probably used for cross-referencing at this point and if Patch 3 ever comes out, it will contain rest of the "customer bugs". However, since it is Gobo probably that gets to work on this "bugworks" I have high hopes we will get further patches, because I presume they are not so occupied at the moment with other projects as Birmingham or other "big" subsidiaries probably are.
BackwardsSuggestions
Member
Damn I'm slow. Can't get higher than 22nd on Practice with TR. Algasuari was 4th!
All settings off besides ABS. Would that cause me to be slower or do I just suck? (Professorial difficulty)
All settings off besides ABS. Would that cause me to be slower or do I just suck? (Professorial difficulty)
Who said the customers found 200 bugs? The QA team found those bugs and they devs have been squashing them since the game went gold.
This is usually how the process works:
Make game
Game goes gold a few weeks or so before release
Devs work on bugs they found that they could not get squashed in time for gold.
Game comes out
Devs release patch
Now Codies aren't Masters of Code like they claim but still, cut them a bit of slack.
drugstore_cowboy
Member
Should I use the Logitech driver/G25 mode with a Fanatec or is there an ingame profile for G25 to select, amar?
Yup, exactly. When last year they knew they only had three patches to get the game as best they can and they STILL had bugs they knew about when it went gold (basically bringing that number down to two) they lost any respect I had for them completely.
F1 fans have given them a mile since the first game and they've taken five. Any flack and repercussions they get from releasing such a stripped down, unfinished game compared to last year is totally deserved.
Hey DrugC, if you ask me for PC version, I have no idea to be honest.
I am playing the game on PS3 at this point and all my settings are related to PS3 - game recognizes CSRE as G25 and it is only profile available.
For actual wheel, on the PS3 you can only select PS3/G25 mode AFAIK (one dot), because game will not react for the wheel in PC mode (no dot).
Have I understood your question well?
This works on my G27, thanks.
drugstore_cowboy
Member
Sorry amar, I thought you were talking about the PC version earlier.
So I ended up ponying up for this, finally had the guts to try running it because hey, that patch would've had to fix a fair bit, right? First go, I shit you not, I get this:
Turns out, there's a 6 page thread on the issue over at the CM forums, that's not counting the other two page thread that was locked because of duplicates.
Jesus fucking christ.
Turns out, there's a 6 page thread on the issue over at the CM forums, that's not counting the other two page thread that was locked because of duplicates.
Jesus fucking christ.
TJP
Member
That really does suck Shane; at least Codemasters are working to fix the issue based on the forum posts.
No doubt you've tried all of these steps: https://support.steampowered.com/kb_article.php?ref=5483-YUFN-0521
No doubt you've tried all of these steps: https://support.steampowered.com/kb_article.php?ref=5483-YUFN-0521
Can't say I have, but I kind of stopped bothering once I saw that there were 6 pages of people with the same issue :/
I really do honestly think that this will be the straw that breaks the camels back. I can see how some people would've been "Okay, we'll give them one last go with 2012" but rather than at least keeping everything the same and even if you don't encounter any bugs, they've managed to remove content between revisions.
I'm looking forward to when it runs well, but I'm not exactly sure when that will be... if ever.
I really do honestly think that this will be the straw that breaks the camels back. I can see how some people would've been "Okay, we'll give them one last go with 2012" but rather than at least keeping everything the same and even if you don't encounter any bugs, they've managed to remove content between revisions.
I'm looking forward to when it runs well, but I'm not exactly sure when that will be... if ever.
Can that be driven through or is that *solid* solid?
Diablohead
Member
don't you hate it when people build walls through a track like that
Oh, apparently there's a bug that causes a lower framerate that will get fixed in a patch next week. That's the next patch that comes out. So if they manage to find the problem with Error 41, the earliest I'll get to play it is sometime next week. Maybe.
Fucking hell. I can't think of a game that required so many patches to fix literally game-breaking bugs at launch than this. Even 2011 wasn't this bad.
Fucking hell. I can't think of a game that required so many patches to fix literally game-breaking bugs at launch than this. Even 2011 wasn't this bad.
TJP
Member
Codemasters have nerfed the performance with patch #2? I noticed a frame rate reduction when I ran the benchmark test and thought I'd overdone replacing the default cars liveries with high defintion versions as some are over 100MB vs the original size of 5MB.
Apparently. And regarding the Error 41, I suspect it may be due to an updated database that the game refers to. One dude mentions that when he uses a different one that allows him to start as one of the big three in career mode, it works. I don't know whether that's because it's an edited one or just one from an older version, but something's changed in that file that causes it to crash out.
TJP
Member
All these issues you are having are the Gods telling you to buy Game Stock Car 2012 
With bugs being discovered regularly in F1 2012, I'm even more glad that CM are now using Steam as it hopefully results in getting fixes in less time. Console gamers will hopefully not be disadvantaged by the 2 patch then pay limitation imposed by MS (not sure about Sony).
With bugs being discovered regularly in F1 2012, I'm even more glad that CM are now using Steam as it hopefully results in getting fixes in less time. Console gamers will hopefully not be disadvantaged by the 2 patch then pay limitation imposed by MS (not sure about Sony).
Shh, I have enough driving games already
But I think console users will definitely benefit from it, because it means that patches can be largely "tested" (totally appropriate word here) by PC users and packed into "service packs" that may fix several hundred bugs, rather than just two hundred (those numbers still astound me).
Oh, something else I found on the CM forums as well:
Honestly. There seriously couldn't have been ANY testing on this game done at all. I'm tempted to try and fire up the game again to look at the credits to see if there were any testers.
But I think console users will definitely benefit from it, because it means that patches can be largely "tested" (totally appropriate word here) by PC users and packed into "service packs" that may fix several hundred bugs, rather than just two hundred (those numbers still astound me).
Oh, something else I found on the CM forums as well:
Honestly. There seriously couldn't have been ANY testing on this game done at all. I'm tempted to try and fire up the game again to look at the credits to see if there were any testers.
Finally got the game, and it started already bugged. LOL Weird framerate, no sound and no button (keyboard and controller) were working. Had to "CTRL + ALT + DEL", and suddenly everything went normal.
Anyway, bough 2010, 2011 and now 2012, and never had many problems with this series, wich I love, BTW.
Anyway, bough 2010, 2011 and now 2012, and never had many problems with this series, wich I love, BTW.
I just found this picture on another forum, can anyone tell me whether they're using the "high" resolution texture pack settings? Because looking at that "N" on the front of Vettel's car, there's nothing high-res about those textures.
TJP
Member
TJP
Member
It might well be a HD paint; it depends where it came from.
High definition paints can be found at RaceDepartment; I've downloaded all of them and quality varies from good to brilliant and many paints are now being upsized to 8192 or 'double HD'. Be aware that performance can take a hit with higher res paints; one can just change the 'high' folder which is your car whilst the 'low' is the game controlled cars.
I've also found changing the shadows from Ultra to High (every other graphics setting set at their maximum) added 12fps which more than offset any fps losses from HD paints. Based on the in-game benchmark test, I lost 3-5fps from installing all available HD paints (10 teams from memory). Prior to using HD paints, I had an average of 67fps with unadjusted Ultra settings at 1920x1080.
TJP
Member
Patch #3 might have been released as Steam downloaded 70MB for F1 2012.
After patch #2, a check of the game_version.txt (\Steam\steamapps\common\f1 2012\game_version.txt) file showed: const char * version = "Master Universal.815819 25/09/2012 19:41 "; unsigned int versionNumber = 815819;
The same file now reads: const char * version = "Master Universal.818459 28/09/2012 12:50 "; unsigned int versionNumber = 818459;
The f1_2012.exe file has changed to v.1.2.0.0 from f1_2012.exe v.1.1.0.0
After patch #2, a check of the game_version.txt (\Steam\steamapps\common\f1 2012\game_version.txt) file showed: const char * version = "Master Universal.815819 25/09/2012 19:41 "; unsigned int versionNumber = 815819;
The same file now reads: const char * version = "Master Universal.818459 28/09/2012 12:50 "; unsigned int versionNumber = 818459;
The f1_2012.exe file has changed to v.1.2.0.0 from f1_2012.exe v.1.1.0.0
TJP
Member
Codemasters have posted a potential fix for the Steam error 41 message: http://community.codemasters.com/t5...eiving-the-Error-41-on-Steam/m-p/102144#M2443So I ended up ponying up for this, finally had the guts to try running it because hey, that patch would've had to fix a fair bit, right? First go, I shit you not, I get this:
"Thanks again for your patience on this issue. We've recieved another possible workaround from our QA team.
In the Steam library right click F1 2012
Click Properties
Click SET LAUNCH OPTIONS
Type safemode
Click OK
If you are able to get the game to boot correctly you should be able to manually adjust the game's settings to suit the performance of your PC. You can then remove the safemode flag from the launch options."
Yup, ATI! There were massive problems with 2011 as well, where if you were using multiple ATI GPUs, unless you disabled Crossfire completely you couldn't get DX11 at all. I miraculously found out how to get it to work only a few months ago, but there was never any acknowledgement from Codemasters that there was an issue, let alone a fix.
And yeah, it astounds me how many bugs they've managed to find so far, especially considering the game hasn't even been out two weeks yet. I'm guessing the benefit to them going with Steamworks this time is that they can release a shitload of patches for PC, see what works and then roll all those into a smaller number for it's console cousin. Still, shouldn't have to deal with *any* patches after a game releases, let alone ones that fix a few HUNDRED bugs :/
TJP
Member
Wow. Nice work Codemasters! Surprised you bought the 2012 game with that kind of support.
Patch notes are up: http://community.codemasters.com/t5...sion/Patch-3-News-02-10-12/m-p/103402#U103402
This update addresses a number of issues, including:
- Fixed an issue with frame rates that was introduced in patch #2
- Fixed an issue where using a flashback could result in an engine blowout effect. This would also result in the player doing an unnecessary pit stop if they were trying to serve a drive through penalty.
- Fixed the achievement The Equipment May Be The Same to unlock in Career as per the description
- Reduced the amount of starting fuel that the user is given for races Austin as it was previously too high
- Fixed some issues in Co-op Qualifying when only one user progresses to the next session
- Fixed a number of camera and graphical issues
- Fixed several issues which would display the incorrect number of players in a lobby or a race
Diablohead
Member
All these patches and fixes are nice but it should have all been fixed for release, and without sped up tyre wear I just can't my mind into buying 2012.
Jamesways
Member
Right?
That's one thing Shift and Race Pro did right, one button clicks for Hud during the race.
I run with HUD off, but sometimes want to see what lap it is. It'd sure be nice to get that info quick.
TJP
Member
I'm glad you got it sorted and once again I'm not surprised to read the cause & fix is the same from a previous game. Have CM announced a crossfire fix?
I'm currently in love with the career mode as the racing has been brilliant.