the one he's talking about has no bearing on whether or not people get daily updates before they get updates. Look under where it says beamng.drive under my name, picture. I'm not in any special testing group, I just set it to that in the profile settings. As far as I know anyone with the alpha can.
It's under permissions groups. I've tested early alpha games before, and I have to agree, you need to be the right kind of person. You learn to make frequent backups, and you fill your desktop quickly. It's a very rewarding job. While I don't have time right now, if you still need them in summer I would be available.
Oh I'm sure we could have a regular old bashfest that would be anything 'but' boring given enough people racing the D15! Might not make many laps but ... that wouldn't be intention entirely.
Yeah, like I said, I am too busy doing nothing to do anything like that. Even if I wasn't busy doing nothing, I don't think I would want to turn the game into a job(if you get what I'm saying). Anyway, thanks for clearing it up everyone. I feel like an idiot now. Edit: Yeeeaaahhhh. Got it.
We do not mean to exclude anyone from cool new content or features; this is just the necessary stage of quality control before we release it to our customers For example the other day we found a bug with the lap timing; it does not adjust for reduced simulation speed, so those with slower computers are put at a huge disadvantage. It is an easy fix and not a bug we would want the public to have to experience And I myself prefer the slower cars; more margin for error, and closer races! Although nothing beats hauling ass at 150 mph on East Coast USA in the Bolide 390 GTR with trees whipping by, until a turn sneaks up on you and you wrap it around a bridge support. There was a seriously competitive back and forth around one of the layouts of the Industrial track between Mythbuster (Tom) and LJFHutch (Sam). Sam set a 49.09 or something initially. By the end of it the fastest lap was a 46.77 by Tom All in the name of research I can't even drive my own car that well. These guys are insane, they keep wrecking my lap times. The only thing I'm still king of the road in is the Moonhawk Special, but knowing Sam's tendency to randomly beat my times by a second or more, that'll be temporary
Yeah, the Bolide is really getting there with the newer updates, it's pretty cool. I gotta admit though, at the end of that 46.77, the car was completely ruined... Had to slam it through the corners so fast that the rear lights bit and the front bumper were missalligned I doubt I'll be able to beat that any time soon, even if Sam beats it. EDIT: Aaaaaand Sam beat me with 46.76...
Gabe and I are in the same boat. I prefer racing the cars that would be a more "realistic" situation for an average joe. Affording a Honda Civic/Older BMW/Older Volvo/Older Mercedes and autocrossing/street racing them is what I am more excited for . Not to mention the parts will be cheaper on them in real life (and hopefully the game).
I'd like to add to, to the problems discussed with high speed stability of the cars; there are also the aerodynamic properties of the cars that are being neglected. Other than that, BeamNG is pretty spot on with its simulation.
Estama has the slowest PC, which is good for making the code as fast as possible, but not so good for enjoying the game
specs? (if you know) i imagine it can't be TOO, bad, unless of course its a weak laptop, in which case, disregard the "it can't be too bad", lol
I think he has an AMD Athlon 3000+. Not sure on the other specs, but I know he can only get about 20 fps with 1 pickup.
I don't know exactly what my colleagues have, but here's my setup: Core i7-3820 3.6 Ghz 8 GB DDR3 GTX 580 Windows 7 x64
The 3820 was much cheaper at the time, I believe. I needed an emergency new motherboard and CPU ASAP since one or both had failed (this was several months ago). Computer wouldn't even boot. Had an i7 960, but that processor's dead now. My current dumb motherboard's default setting is to overclock my processor (the 3820) to 4.4 Ghz, causing it to overheat and freeze/crash, with an "OVERCLOCKING FAILED" message on reboot. I finally went into the BIOS and turned the clock multiplier back down to 100 so it wouldn't overclock it to failure constantly. It's liquid cooled but can't handle 4.4 for whatever reason.
probably because the 3820 isnt a k series cpu, so therefor isnt actually supposed to be as freely overclockable as something such as the i5-3570k, or i7-3770k or something of that sort, although, non k series cpu's can be overclocked, just not even close to as freely as a k series cpu
