I realize this post will not be popular with the devs, but guys... its pretty bad. I hate to say that and I know a TON of work goes into this. I was in love before the update. Sure, wheels wobbled a little but thats ok. After the update, my controller didn't work at all and now that I've re-installed everything, roughly half of my controller controls work. The bigger problem is that 3-5 seconds into playing it freezes. I can still rotate the camera around but the car is frozen. I made a quick video. (It froze when the truck stopped rolling) http://s42.photobucket.com/user/wr200/media/BEAMCRASH_zps4c4e46dc.mp4.html My pc played it beautifully before the update. i5 3570k, 1gb graphics, asrock 4 extreme mobo etc. I know, I know... it's alpha. Yeah I get that but an extra trial run or two might have really helped. Maybe its my fault for jumping on the update. Anyway what can be done about these issues? Can all of us having issues revert? thanks
Ok I'll give it a whirl. I did as you said. Fully updated. I have no steering, otherwise controller works. Game froze 12 seconds in. I don't know what it means but "enabled" in the upper right corned read "no".
if your using a costum inputmap, thats the problem. the steering was renamed from "joy_steer" to "steer" and the Bind-command was changed to "%mm.bind" with the new update.
Yes sir. I was using a custom map and here it is: I think I see how to change the steering but what was the old bind command called or could you put it in bold for me? edit: I changed the it to "steer" like you said and now I have (really good) steering! I could kiss you if you're a hot girl. Still dont know what bind is or how to change it but whatever; seems to work. // Product Name: Controller (Xbox 360 Wireless Receiver for Windows) // GUID: {02A1045E-0000-0000-0000-504944564944} // axes: 5^Y^X^U^R^Z // 15% deadzone for the camera things $gp_deadzone = "-0.15 0.15"; // camera moveMap.bind(%device, thumbrx, "D", $gp_deadzone, gamepadYaw); moveMap.bind(%device, thumbry, "D", $gp_deadzone, gamepadPitch); // movement : deadzones and such are in lua for these moveMap.bind(%device, thumblx, "D", $gp_deadzone, joy_steer); moveMap.bind(%device, triggerl, "D", $gp_deadzone, brake); moveMap.bind(%device, triggerr, "D", $gp_deadzone, accelerate); moveMap.bind(%device, btn_l, clutch ); moveMap.bind(%device, btn_a, shiftUp); moveMap.bind(%device, btn_x, shiftDown); moveMap.bindCmd(%device, dpadd, "beamNGResetPhysics();", ""); moveMap.bindCmd(%device, dpadr, "beamNGTogglePhysics();", ""); moveMap.bind(%device, btn_r, parkingbrake_toggle); moveMap.bindCmd(%device, lpov, "beamNGSwitchVehicle();", ""); moveMap.bindCmd(%device, btn_y, "gamepadZoom(-0.1);", "gamepadZoom(0);"); moveMap.bindCmd(%device, btn_b, "gamepadZoom(0.1);", "gamepadZoom(0);"); moveMap.bindCmd(%device, btn_rt, "beamNGResetCamera();", ""); moveMap.bindCmd(%device, btn_back, "beamNGCameraToggle();", ""); //moveMap.bind(%device, btn_back, beamNGControl); //moveMap.bind(%device, btn_x, toggleFirstPerson);
i meant "moveMap.bind" at the beginning of every line, should be changed to "%mm.bind" but since it seems to work for you that may be not necessary
Sorry for the problems guys, buts its an alpha test access: we are working on fixing these things. We will not upload or support old versions as that would only increase our work load.
Seems like it would be easy to leave the old version up after uploading the latest? I know you guys are busy, but several of us can't play the game, whereas we could on the previous version. And if it's another three weeks until the next update, well... that's just disappointing. Do what you must do. I am only posting because you are doing amazing work and I can't stop playing with it.
I would love to have such a history too. Too bad probably nobody made a backup at each stage. I know I'm going to make these from now on. My reasons are beating the current record in Coovargo's Small Island Challenge (which was done with the last version) and the Oculus Rift Support. While this is not good practise in a project's development, I understand the dev's position to some small degree. There is still the option of making a separate install with the 0.3 installer.
I didn't think about reinstalling using the previous installer. Will give that a shot and report back if it properly reverts me.
yeah come to think about it, I think I have my old file too, if its the one that 218MB vs the new 220MB.
It doesn't appear that the core .exe is actually included with the installer... it requires connecting to the web and getting the latest version via the updater in order to play. So, no go on reverting, unfortunately.
We have a valid point in not offering old alpha versions: the support load. It additionally segregates the community. If you continue playing with the old version and you notice a problem, it is impossible for us to fix it. It only works well if everyone uses the latest version. Please understand that we are 4 people who want to fix any problems up as fast as possible, but some things take some time and others will be broken even if they seem to be fixed and working well at some point. The goal for us is to have a better final game after those changes, not to annoy our paying customers as some of you might think :-/
Well, I am thankful for you guys putting in the hard work you are. I understand there will be bugs since this is still in Alpha. I knew that when I paid for it. We just need to be patient, let you guys do your work so we can have a totally awesome game when it's finally in full release. Keep up the great work you guys are doing. I appreciate it.
Nobody asked for support on old versions. As far as I care you can leave the auto-update and really everything as it is, and only create a public access but semi-hidden archive with the old patches for those few that care about the history for some reason and search for it. Don't you have this for yourself?
I don't think anyone is asking you to support the older versions if we find bugs. It'd just be nice to optionally run an older version when a newer one is completely broken. With the automatic update system you have in place, however, I can see how it is more than just a simple "put up the old install.exe" to even make the older versions available. I'll just hope that the Momo wheel bug is fixed in the next update...!