I have some bits of Qt networking + OutGauge code laying around somewhere in case you need it...
I'm not sure what the default behavior of Windows command prompt is, but if the program's execution is paused, the OutGauge packets are buffered until the program resumes. The program would then read the buffered packets first which would look like a delay on the output.
The source you're experimenting with uses the old OutGauge format. Refer to LFS/docs/InSim.txt for the new format.
He has 6 cores, Windows sees 12 logical CPUs because of HyperThreading.
Actually, I wonder if Taavi's high benchmark score can be (partly) accounted to the Windows scheduler not being able to work well in this complex environment where some CPUs share caches and some CPUs aren't really CPUs.
Linux benchmarking tool that let's you measure the peformance of LFS under WINE.
https://dl.dropbox.com/u/37342755/LFSLinBench.tar.xz
https://dl.dropbox.com/u/37342755/LFSLinBench.tar.xz
For those who are actually willing to give it a try, it should be noted that it's not possible to use Fraps as a benchmarking tool with WINE. There is a less accurate LFS-specific workaround available, but it's not "production-ready" at the moment...
Does this help?
- Set the wheel's range to whatever value you want in the Logitech control panel
- Set "Wheel turn compensation" in "Options - Controls" in LFS to zero
- Click "recalibrate axes" and turn your wheel fully from lock to lock
- Make sure the calibration lock is set to "unlocked"
- Set "remove deadzones" to "yes"
I don't think the post rating has anything to bring to the table. You can always report spam or other inappropriate posts. IMO the whole "user rep" thing is nothing but a form of eMasturbation for forum addicts. Since there is no way how to make people use the + / - rating responsibly, I guess it would just make the forum harder to moderate, aka "That ban is unfair, I got all my minuses from him"
If your FPS drops with the number of cars on track increasing, it's your CPU. Make sure it's not overheating. IIRC a perfectly fine P4 3.2 GHz can handle a grid of about 15 at 20+ FPS easily.
BTW, how can you be running a 64bit Windows and have only 3.5 GB of RAM usable? Apart from P4 6xxx series, those CPUs weren't 64bit anyway.
BTW, how can you be running a 64bit Windows and have only 3.5 GB of RAM usable? Apart from P4 6xxx series, those CPUs weren't 64bit anyway.
Why do you assume this analogy is valid? You have no idea what Eric has been up to (if he's been up to anything at all). By this logic, you will have set up about 29 home theatres by the end of the year and somehow I don't think that's what's gonna happen.
Let me offer you another explanation. Scawen has never mentioned that he's using some versioning system, so I'm gonna go with assumption that he simply copy-pastes LFS' source whenever he needs to create a new development "branch". One branch has the Scirocco, Rockingham, unfinished tyre physics and all that classified stuff you claim that exists. The other branch is just the old 0.6B source with no updates whatsoever. He doesn't want to backport all those content-related changes into the old branch because it would mean a lot of work, debugging, fixing problems reported by the community and merging those fixes back into the development branch. The development branch is, however, too buggy to be released and the changes too tied together to simply remove the problematic parts.
I'm pretty sure you don't believe this explanation, but it's based on the same logic you've been using in this thread.
If there was a reward for jumping to conclusions and pulling stuff out if one's arse, you'd be a pretty hot candidate to get one. I know this is the interwebs where anybody can post anything, but what if someone new or unfamiliar with how things are around here reads this? Your last posts in this thread suggest that there's a brand new ultraawsome version of LFS on Scawen's HDD, but he refuses to release it because he's obsessed by the tyre physics programming. That simply is not true. Your It could have happened, therefore it must have happened kind of reasoning is really stupid an annoying to read.
V1.05 is up. At last it should play nice with all other USB HID devices...
Have you tried the application I posted above? If nothing else it would be interesting to see what kind of results would it return on a machine with supposedly incorrect RTC clock.
160! * LOL... Did I somehow miss the part where mankind has evolved into a state where a relationship on Facebook actually means something?
Seriously, dude, you're getting way too worked up over this. 4 months is nothing and the girl apparently doesn't know herself whether she wants to date you (or anybody else for that matter) or not. That's why she's acts all strange and illogical... just let it go.
You can't possibly know that. You have no idea what kind of advancements has Scawen done since the last update. The patch can be released tomorrow, next week... or next year.
You know, with people whose attitude is similar to yours around it's no wonder Scawen doesn't bother with any progress updates...
I love how the NFS series has been running in circles ever since Most Wanted. Tuning yes, tuning no, cops yes, cops no, extra (stupid) powerups are the way.. oh, wait, they're not, and now it seems like they resurrected NFS 3... or HP 2... or the "second" HP without powerups. I wonder how can this series still make money...
The only thing that might (and probably will) happen is that Windows will keep some files and config created for the old board. You could probably just uninstall any software that came with the old board, do the swap and hope for the best. If you notice any problems like random crashes, funky USB or slow performance, you can always do a clean install.
And just a side note, I don't think that Windows has gotten any better at handling this kind of things over time so the procedure should be the same for anything from W2K to W8...
And just a side note, I don't think that Windows has gotten any better at handling this kind of things over time so the procedure should be the same for anything from W2K to W8...
When "Will you help me?" means "Will you do all the (hard) work for me?", you really can't expect people to go head over heels trying to accommodate you.
What Shotglass is trying to say is that there's no measurable lag caused by the CRT screen itself and that's consistent with John Carmack's findings.
MS have been doing some weird decisions lately. Is this their way of getting people write apps for the "cool" Metro? Do older versions of MSVS work under Win8? I also hear they decided to mangle C++11 support in MSVS 2012. Not much, but enough to create issues when people will try to build their code on other platforms. God knows why I try to stay away from MS stuff as far as possible
Rant aside, what does this mean for .NET developers?
Rant aside, what does this mean for .NET developers?
Let me give you a little real-life example why I think this approach is not a good one. Some year and a half ago I built a kinda mean gaming rig for my sister. I used the most up-to-date parts available at that time including i7-950 and X58 chipset. If you check the CPU market right now, you'll find out that there's no way I could upgrade a CPU in that thing - Sandy Bridge needs 60-series and Ivy Bridge 70-series chipsets. Today's market evolves too fast that even 18 months old parts are "outdated" and pretty much unupgradable.
Upgrading an old computer is like running a 20 years old car. There will be periods of time when the car will work fine, but then something will break down, you'll get fixed, drive it for a while waiting for something else to give up. In the end you'll spend so much money on maintenance that getting a whole new car would be cheaper.
If I understand John's explanation correctly, there was an 8 ms lag on the part of the USB controller (probably due to polling rate) and additional 30 ms lag caused by the LCD screen and quite horrible horrible extra 60 ms lag when he tested the Sony's 3D contraption.
That's not a particularly good approach. Even if you get the best MB available today, chances are you won't be able to just put a new CPU in it after a few years. New CPUs are almost never backwards-compatible, they require new sockets and chipsets which in turn don't work with older RAM modules... you know
I suggest you get the best machine you can afford and don't care about upgrading possibilities. I've never upgraded any of my PCs except for adding more RAM and bigger hard drives (I upgraded GPU once but that was only because the old one died). At the end of the day you'll find that the upgrades cost you almost as much as a new PC.
I'm afraid I can't think of anything directly programming or deleting related (although I accidentally shift-deleted some stuff into oblivion lately), but I remember this blow up when I was migrating a Drupal-based website from one server to another.
For those who are unfamiliar with Drupal, it keeps almost all its dynamic content in a SQL database. The server I was migrating the site to was a sort of testing installation where I tweaked and reworked quite a lot of things, so I only wanted to move the tables containing content and user data. Now those tables don't really have a primary key, so when I carelessly - sipping my coffee and conversing with a friend - launched the copying operation in SQLFront, I effectively nuked the DB. I spent like 4 hours trying to figure out what went wrong, messing with things that were in fact working just fine, raging at the Drupal devs for not having a better migration system, before it occurred to me that there is probably something oddly wrong with the DB. Restoring the DB from a backup, copying the tables again (correctly this time) and ironing out a few glitches took about 30 minutes - talk about artificial problems
For those who are unfamiliar with Drupal, it keeps almost all its dynamic content in a SQL database. The server I was migrating the site to was a sort of testing installation where I tweaked and reworked quite a lot of things, so I only wanted to move the tables containing content and user data. Now those tables don't really have a primary key, so when I carelessly - sipping my coffee and conversing with a friend - launched the copying operation in SQLFront, I effectively nuked the DB. I spent like 4 hours trying to figure out what went wrong, messing with things that were in fact working just fine, raging at the Drupal devs for not having a better migration system, before it occurred to me that there is probably something oddly wrong with the DB. Restoring the DB from a backup, copying the tables again (correctly this time) and ironing out a few glitches took about 30 minutes - talk about artificial problems
FGED GREDG RDFGDR GSFDG