But they were buggy as hell. The ant that shipped with FC2 was very very quick compared to a normally compiled ant, but sadly fell over all over the shop;(
In which case do the HTTP install, and don't even download that much. I think the rescuecd can function for this purpose, and it's fairly small (about 80 meg).
AFAIK a minimal install only uses the first CD. A default workstation install uses three, but barely touches the last. I don't know what a default desktop install uses.
What crap. Places like the Sahara and Kalahari desert have been populated for donkeys, and they're hardly hospitable. Which inhospitable place were you thinking of specifically that has been populated in the last 200 years?
Not quite the right procedure though. It's not rated for 40C somewhere in the innards. They've reckoned it'll be good enough at cooling itself if the ambient temperature is 40 degrees... Otherwise why not measure the temperature of your desktop CPU and try and match it up with claimed environmental specs.
You are joking aren't you? We've not even got near to PAL/NTSC resolution 'perfect' quality. Until we can produce computer generated imagery at 800x600 that is indistinguishable from a live TV broadcast, we've got plenty of work left to do.
I assume the L1/L2 controller setup is similar to the Origin 3000 systems. It really was handy for many tasks, although it was possible to power up the system just fine, as long as you knew the order boxes had to appear in, and were fairly swift with the old fingers.
I'd say you're nearly on it there. The problem is one of jitter. Frames are not calculated for the exact moment they're going to be displayed. On the Amiga, you'd design your 3D game to be 25fps or whatever, and you'd know it was always going to be 25fps, since you made sure that was always the case by changing the level design anywhere you can't maintain it. There was no jitter, since you were displaying frames aligned with the refresh rate.
Now with varying hardware, and tougher 3D graphics you enter into a problem where you've no idea how long it'll take to calculate the frame. Do you assume that it'll fit within one refresh, and thus calculate the frame for now + 1/72th second (or whatever), or do you think it'll take two frames and go for 1/36th? Or do you just sod it, and calculate for now and get meaningless 200fps where more than half the frames are never displayed?
The real trick is to calculate a few frames ahead to smooth out the hard from the easy, and to try and remove that jitter by varying when you're generating a frame for. Syncing buffer swaps with the monitor sync is a given.
People like to make complicated issues simple, which is where the 30fps myth came about. It's much more complicated than that. 30fps where objects are moving in the z direction almost always appears smooth as butter, but 30 fps with things moving across you (either x or y) and you'll be far more likely to notice it. You'll get into problems if you start to use spare power for AI, since the game will get harder the faster the processor (IYSWIM).
You've certainly been seeing something I've not. I've never heard a developer complain about OpenGL being hard to code in, but I've certainly heard abuse hurled at the whole DirectX malarky. What DirectX does have going for it is the fact it covers not just graphics, but sound, networking, and input devices.
Personally I found OpenGL to be complete and utter bliss to use.
Extremely underpowered? It's about 8000lbs and it's got 350hp (unless I'm looking at the wrong car). That's not radically different power:weight than a lot of small cars.
Then you're clearly a lucky bastard. IA32 kernel is compiled with the 4K stacks option which breaks Nvidia drivers. Nvidia admit this, maybe you should.
So I guess the running IBM T220 off a Quadro FX3000G at 3840 x 2400 is a figment of my imagination. With the new FX4000 you can run it off a single DVI connector. I'd not read anything to suggest this is breaking the DVI spec.
If you don't bother reading the benchmarks then fine, you're right. In some of the benchmarks posted on Tomshardware you are seeing up to double the performance (at high res, with aniostropic filtering). Overclock away, smoke boy.
In an environment when we do not have a unified tax system across Europe, I hope you understand why the UK government doesn't want this.
Once you break those barriers, lots of indirect taxes become useless, since you can trade around them. But if you are after a federal europe, then I guess I can't quibble.
Vsync isn't the same with 2D. For it to work, everything has to be properly double buffered, which it isn't. This isn't something that is [just] fixed by a change to the graphics drivers.
Again compiled for, doesn't mean exclusively for. They've optimised for P4, compiled for 586.
But they were buggy as hell. The ant that shipped with FC2 was very very quick compared to a normally compiled ant, but sadly fell over all over the shop ;(
In which case do the HTTP install, and don't even download that much. I think the rescuecd can function for this purpose, and it's fairly small (about 80 meg).
AFAIK a minimal install only uses the first CD. A default workstation install uses three, but barely touches the last. I don't know what a default desktop install uses.
What crap. Places like the Sahara and Kalahari desert have been populated for donkeys, and they're hardly hospitable. Which inhospitable place were you thinking of specifically that has been populated in the last 200 years?
What do you think the sub 40 quid digiboxes are in the UK? It's not like everyone's gone out and bought a new tv...
Not quite the right procedure though. It's not rated for 40C somewhere in the innards. They've reckoned it'll be good enough at cooling itself if the ambient temperature is 40 degrees... Otherwise why not measure the temperature of your desktop CPU and try and match it up with claimed environmental specs.
Hell, I chose to buy a house close enough to work that I walk in every morning. A small car would be a big step in the wrong direction ;)
You are joking aren't you? We've not even got near to PAL/NTSC resolution 'perfect' quality. Until we can produce computer generated imagery at 800x600 that is indistinguishable from a live TV broadcast, we've got plenty of work left to do.
I assume the L1/L2 controller setup is similar to the Origin 3000 systems. It really was handy for many tasks, although it was possible to power up the system just fine, as long as you knew the order boxes had to appear in, and were fairly swift with the old fingers.
I'd say you're nearly on it there. The problem is one of jitter. Frames are not calculated for the exact moment they're going to be displayed. On the Amiga, you'd design your 3D game to be 25fps or whatever, and you'd know it was always going to be 25fps, since you made sure that was always the case by changing the level design anywhere you can't maintain it. There was no jitter, since you were displaying frames aligned with the refresh rate.
Now with varying hardware, and tougher 3D graphics you enter into a problem where you've no idea how long it'll take to calculate the frame. Do you assume that it'll fit within one refresh, and thus calculate the frame for now + 1/72th second (or whatever), or do you think it'll take two frames and go for 1/36th? Or do you just sod it, and calculate for now and get meaningless 200fps where more than half the frames are never displayed?
The real trick is to calculate a few frames ahead to smooth out the hard from the easy, and to try and remove that jitter by varying when you're generating a frame for. Syncing buffer swaps with the monitor sync is a given.
People like to make complicated issues simple, which is where the 30fps myth came about. It's much more complicated than that. 30fps where objects are moving in the z direction almost always appears smooth as butter, but 30 fps with things moving across you (either x or y) and you'll be far more likely to notice it. You'll get into problems if you start to use spare power for AI, since the game will get harder the faster the processor (IYSWIM).
You've certainly been seeing something I've not. I've never heard a developer complain about OpenGL being hard to code in, but I've certainly heard abuse hurled at the whole DirectX malarky. What DirectX does have going for it is the fact it covers not just graphics, but sound, networking, and input devices.
Personally I found OpenGL to be complete and utter bliss to use.
10 Gbit is fairly normal for academic networks, nothing out of the ordinary.
k _P erformance/bbone-traf-diagram-2003-04-28.pdf
The JANET backbone in the UK is 10Gbps where it matters, but the load on the network still isn't that great.
Some interesting figures can be found below
http://www.ja.net/development/End_to_End_Networ
Extremely underpowered? It's about 8000lbs and it's got 350hp (unless I'm looking at the wrong car). That's not radically different power:weight than a lot of small cars.
So is this all about retribution for 11/9? Do you think the families wanted death and destruction on a scale far larger than a couple of buildings?
Or just recompile the kernel with the 4k stacks option removed, or download the binaries that are available.
Then you're clearly a lucky bastard. IA32 kernel is compiled with the 4K stacks option which breaks Nvidia drivers. Nvidia admit this, maybe you should.
There's a variety of attacks that levels the field, but a managed switch has the potential to rise above a hub for security.
So I guess the running IBM T220 off a Quadro FX3000G at 3840 x 2400 is a figment of my imagination. With the new FX4000 you can run it off a single DVI connector. I'd not read anything to suggest this is breaking the DVI spec.
If you don't bother reading the benchmarks then fine, you're right. In some of the benchmarks posted on Tomshardware you are seeing up to double the performance (at high res, with aniostropic filtering). Overclock away, smoke boy.
But in fairness, what guarantees can you have that it will be that app that gets the OOM?
In an environment when we do not have a unified tax system across Europe, I hope you understand why the UK government doesn't want this.
Once you break those barriers, lots of indirect taxes become useless, since you can trade around them. But if you are after a federal europe, then I guess I can't quibble.
You're right eXceed is completely impossible to setup. Run Exceed. Run putty with X forwarding. Use X.
Vsync isn't the same with 2D. For it to work, everything has to be properly double buffered, which it isn't. This isn't something that is [just] fixed by a change to the graphics drivers.