Sorry to steal this thread, but I’m getting the same error code. As suggested, I moved my car folder outta dodge, and the game started fine. I then copied one car back (model and trim files) to the save folder and the game started. All good so far. Copied save content back, and it threw the error msg. Is there a way, besides moving each one individually to find the guilty party, to tell which file is causing the hiccup? Like the file date, or is it alphabetically processing the conversion to the new format?
Again, apologies, but I felt this was related.
—EDIT
Never mind. All fixed. Moved trim files in batches, found the issue. Had a dud trim.
Same here. It seems that with the arrival of the new beta release the test track driver also received an update in self preservation. The car will not go intro 3rd. Also, rather strange, at top speed the graph show that the brake pedal is fully pressed and the throttle is not pressed at all, and still the car is able to go at 100kmh the entire straight of the Automation Test Track.
I’m sure this will be solved quickly. I like the new update. rh4d00_bhp - Dacia.zip (88 KB)
[quote=“AlternateSteve90”]X-posting this topic, because I really need some help ASAP. viewtopic.php?f=16&t=7976
[/quote]
If you’re having trouble with your Steam version of the game it’s probably not Steam’s fault
I would recommend getting to a clean slate install in this case: remove/delete your whole Documents\My Games\Automation folder, then go to your Steam library and right-click Automation → Properties → Local Files → Verify Game Cache
Then start the game and tell us what errors pop up, if any.
[quote=“jagermeister”]Cars won’t go any faster than 60 on the test track, or won’t shift up past second gear.
Changing the price on any car will crash the game.[/quote]
What error message do you get when doing that (changing price)? Is this on a newly built car or an old one from the previous big update?
Something is wrong with the awd calculations. I’m getting the same 0-60 time, within a tenth of a second regardless if it’s 100%f 100%r or anything in between. It also has almost no effect on the stats as I change the distribution.
Just checked and what seems to happen is that acceleration doesn’t change from 99% to 1% rear power distribution, and it becomes slightly better when the power distribution is 100% rear or 0% rear.
Wheel spin seems to vary properly.
I tried a car with huge semi slick tires and a 30hp engine, as well as a car with a 800hp engine on tiny hard compound tires and they both present the exact same problem.
[quote=“jagermeister”]Cars won’t go any faster than 60 on the test track, or won’t shift up past second gear.
Changing the price on any car will crash the game.[/quote]
What error message do you get when doing that (changing price)? Is this on a newly built car or an old one from the previous big update?[/quote]
This little error showed up, accidentally click the right arrow button ( that goes from your cars to company cars) in the companies section with no company selected but that could just be might fault.
Have a few bugs to report, will have more tomorrow.
I get this one when I try to change paint tone (or select one of the 9 default colors). I’m sure it’s come up while doing other things, but I can’t remember right now.
This one was definitely game-breaking. It comes up when I do basically anything in the engine editor. Selecting conrod type, adjusting compression, choosing valve cover, anything. You name it, and it throws this up. If I’m trying to change bore for example, it pops up when I click the slider so I basically can’t adjust bore.
This last one is another common one. It just recently came up while selecting drive configuration, but will happen when clicking the arrow to go to the next screen (and it sometimes will go to the next screen, but more often than not it will not do anything but freeze the game).
One more bug that doesn’t throw a .lua error is that when I try to revise a car (to change the engine, for example) it’ll go to the fixture/chassis editor like normal, but when I click the “Engine” tab at the bottom, the game will jump to it for a split-second then it will jump back to the first screen (where you choose frame type and stuff). If I try to close the editor from here, the game will freeze solid. This happens on the last stable release and is not exclusive to the Open Beta, however.
Of course, these could all be happening because of my PC’s specs or Windows 10, which wouldn’t surprise me.
Thanks for all the bug reports so far! That is really helpful.
We just pushed live a new update for the open beta. I have updated the OP with the changelog.
Cheers!
[quote=“jagermeister”]Cars won’t go any faster than 60 on the test track, or won’t shift up past second gear.
Changing the price on any car will crash the game.[/quote]
What error message do you get when doing that (changing price)? Is this on a newly built car or an old one from the previous big update?[/quote]
I was building that leightweight sportscar from the late seventies, that square ferarri looking thing. I put in a 2.4 litre V6 in it.
Also, I got this error while selecting the closed grille to create a place for a license plate:
Cant place fixtures, if they are from other place, than first visible row. If i click to use those, that are under, they are not clickable nor placable.
Something seems to have happened to many of my Scenarios, they’re just completely gone. Upon clicking on a Scenario category I’m also presented with this Lua error:
[size=85](By the way, I never realized you guys were using tolua++! Your usage of Lua is very cool, I’ve worked with a different game’s engine that made heavy usage of Lua scripting and it’s junk compared to your guys’ stuff)[/size]
Not sure if it is a Open Beta bug because i only got time to play now, anyway, i’m using an very old ATI card (X1800GTO) because my newer card died and got this “small wheel” bug: abload.de/img/legatumserreta-2400-1zvsz5.png
FPS wise the game runs fine on medium details with this old card, which is very nice! The only problem is this damn bug…
Dxdiag.txt file is attached to the post. DxDiag.txt (61.6 KB)
