Relax lol. He's not calling anyone specific an idiot. He's just saying that there may or may not be idiots (griefers) who try to ruin the experience for others and thus there are safety protocols put in place to protect those who don't want their experience ruined by undefined idiots. Take what you want from it.
Cool idea. Maybe a function to "record" a race-line from driving a lap yourself.
Honestly the spectate from false start is very annoying feature when you have disabled midrace joining. In my opinion it should be in administrator's hand how the false start is handled. (For example sending to pitlane)
And yeah. the update is appreciated. As far as the "idiots" (I can say that. I can say that!) on starts goes?
That happened so much with the formula v8's It's probably one of the main reasons no one really puts them on servers.
I only see a "narrow" part from the cockpit (resized screenshot). With a few degrees more FOV the impression would be much better / more realistic for me.
And yes: I also played around with the other options. For example, the pitch view (negativ values around 5°) and the Y offset. But that is only a workaround and not a solution.
But that depends on your display size (inches), not? With a 40+ inches display I don't need to seat so close. The impression would be a bit further back (at 100 °) much better. In addition, it also has an impact on the sense of speed, which is a subjective feeling.
I do not want an "infinite" FOV but only a slightly higher adjustable value (perhaps for 100 or 105°), sometime.
Very happy to see updates still coming along. Works great on my desktop, decided to install on my notebook for at work and wow, it's been a while, and I'm really impressed with how optimized it is. It's a 5200U with HD 5500, and I can pretty much max it out and hold 100fps. Very impressive.
All cars testing offline mod.
Desktop 18.5 inch Monitor 1366x768, fov 94 degree, 2x antialias, af 4x. Hd 3650 graphics card
Laptop have 1366x768 and 7670m but this device no tested.
Also cars with bad indicator rods high refracting for 0.6u. Fonts are worse.
Good cars dashboard graphics report :
FO8: 0.6u better.
MRT: 0.6u better.
FZ5: 0.6u better, but dashboard rods some refreacting.
FXO: 0.6u better, but dashboard rods some refracting.
RB4: 0.6u better.
LX4/LX6 0.6u better.
UF1: 0.6u better, also dashboard rods good quality.
Any way we can get that debounce option for other controls, like up down left and right? Using the rotary dial on my g29 seems.to always yield 2 presses, milliseconds apart, makes it tricky to fine tune pit settings, or toggle whether I want damage repaired
One of the servers i host , crashed today.
Some say it happends during a track/layout change
i hope you can get any information about the errorcodes below:
Naam van toepassing met fout: DCon.exe, versie: 0.0.0.0, tijdstempel: 0x5c89394e Naam van module met fout: DCon.exe, versie: 0.0.0.0, tijdstempel: 0x5c89394e Uitzonderingscode: 0xc0000005 Foutoffset: 0x0001c053 Id van proces met fout: 0xac0 Starttijd van toepassing met fout: 0x01d4ed5b34cecc9b Naam van toepassing met fout: DCon.exe, versie: 0.0.0.0, tijdstempel: 0x5c89394e Naam van module met fout: DCon.exe, versie: 0.0.0.0, tijdstempel: 0x5c89394e Uitzonderingscode: 0xc0000005 Foutoffset: 0x0001c053 Id van proces met fout: 0xac0 Starttijd van toepassing met fout: 0x01d4ed5b34cecc9b
I could see where it crashed in the code but it's a bit mysterious because it is at the point where LFS loads the objects when you load a track.
So that shouldn't happen unless:
1) The file is corrupted. In this case, the bug would come up every time you try to load that track. Do you know which track it was? Are you able to load each track on that server?
2) The computer's RAM is corrupted. This is very rare and would probably be repeatable or cause other random faults.
3) Overclocked computer. The most common reason for memory errors. I'm guessing this is not the case here.
4) It could also happen if a memory allocation failed - LFS isn't checking for that case. It should only normally happen if there is a significant memory leak and the program has been running for a very long time. I have discovered a small memory leak recently but this seems unlikely as we aren't seeing regular crashes from DCon. Unless maybe yours was heavily used for several days?
5) A memory corruption error somewhere else in the program.
At this point I can't think of anything else, as the crash is in code that is used every time a track is loaded. So all I can ask is for you to check if all tracks can be loaded on that instance of DCon.
The Dcon hasnt crashed since then. So i'm thinking of reason 4 and 5 at the same time. The DCon was running since version U came out. Without any crashes.
: