Also having another look at the Eagle, removing the booster, gives you more less the same design as the falcon anyway nd wherever it came from it an impressive piece of engineering
Not doubting any of that.
Other articles I've read do point out the Phoenix as the end of the Falcon development, not that a project only had to have a single predecessor but I do find it interesting that the airframe of the Phoenix looks more like the Falcon's than the Eagle's which maybe more to do with it being a Hughes project.
The radar and missiles were (and still are) impressive, after the F-12 programme ended the radar and missile ended forming the basis of the F-14 (via the F-111B) AWG-9 radar and AIM-54 Phoenix missile, so all that developed effort did not go to waste.
Just to agree with you, one friend left a games job a few years back to be an academic, not a occupation known for paying huge wages and got a nice bump in salary plus much better working hours
Yep, been a paid up member for a while now, The Open Rights Group are also doing good work and are worth supporting.
Right now it seem to bad idea of the week with all these laws, for a bunch of technophobes they sure do seem to have a lot of faith in technology, hopefully they will see sense or at least allow proper debate.
Yeah, Multi-pass is less than ideal right now, I've not seen a really good way to expose it using at the API level (Vertex textures look to be the way to go for that but not many cards you can buy right now support them).
You can do some nice stuff on the PS2, but then you are coding right to the metal and you have to do all the normal driver stuff yourself anyway.
Statefulness:
That an API design thing, I can see why they did it for backwards compatibility. Maybe they should have gone for a clean break
Extensions:
Yep, that a problem.
Vertex buffers:
Reading this it sound like display lists would be a better fit for this.
Render to texture:
Got to agree with you on this, the windowing system intergration is a pain, the ARB seem to agree with ES only having EGL not a lib per windowing system.
Codepaths:
Having been given the lucky job of making a render engine work with a lot of D3D drivers. We had many code paths working around missing feature or buggy drivers, so I don't think making any app work on a broad spectrum of cards is not simple or easy.
Very true, you do have the software failbacks in D3D for everything, OpenGL will only have them for whatevers is in the core spec for that version.
I was not trying to be pro OpenGL, it has it own problems, new stuff taking an age to be added to the core being at the e top of them, but the ARB has been working much faster in the last year/18 months. Hopefully they can keep moving things on.
In D3D you need to check caps bits for feature, OpenGL you need to check if the extension is supported, seems about the same to me.
I don't understand your comment about OpenGL being Stateful, D3D also stores its own internal state and it maybe more than one copy, one for the DX runtime and another in the driver proper.
About the extensions, nothing stops a Radeon (or anyone else) implementing the NVidia extension (which I think they do). OpenGL allows you just to call the new features (if supported). In D3D access the new feature means you will need to move all your calls to the new interface.
Vertex Arrays do the same sort of job as Vertex Buffers in D3D, plus you have display lists so you can combine geometry and state change into a single call.
In the end to support cards with different features sets you are still going to have different codepaths.
AMD have had dual core chips on the roadmap for sometime (I know not the same as SMT/HyperThreading), they will also add SSE3 at the same time.
Do Intel have the on chip memory contoller? or the Glueless 4 Way systems?
Slashdot Mirror
Also having another look at the Eagle, removing the booster, gives you more less the same design as the falcon anyway nd wherever it came from it an impressive piece of engineering
Not doubting any of that. Other articles I've read do point out the Phoenix as the end of the Falcon development, not that a project only had to have a single predecessor but I do find it interesting that the airframe of the Phoenix looks more like the Falcon's than the Eagle's which maybe more to do with it being a Hughes project.
The radar and missiles were (and still are) impressive, after the F-12 programme ended the radar and missile ended forming the basis of the F-14 (via the F-111B) AWG-9 radar and AIM-54 Phoenix missile, so all that developed effort did not go to waste.
Just to agree with you, one friend left a games job a few years back to be an academic, not a occupation known for paying huge wages and got a nice bump in salary plus much better working hours
Tim Moss (lead on the first two God of War games) for one, he was in the Lost Boys demo group and did a few games
Concorde on steroids with more background links.
Yep, been a paid up member for a while now, The Open Rights Group are also doing good work and are worth supporting. Right now it seem to bad idea of the week with all these laws, for a bunch of technophobes they sure do seem to have a lot of faith in technology, hopefully they will see sense or at least allow proper debate.
They can take a DNA sample just by being arrested. Have a look at the Serious Organised Crime and Police Act 2005 for some reasons you can be arrested.
So yes they can take your DNA for speeding but not late library books (yet).
BattleTorrent was the original name for BlogTorrent.
Here, a HP employee response and a business analysis of region coding Cartridges.
Reading protected LiveJournal entries via RSS
Yeah, Multi-pass is less than ideal right now, I've not seen a really good way to expose it using at the API level (Vertex textures look to be the way to go for that but not many cards you can buy right now support them).
You can do some nice stuff on the PS2, but then you are coding right to the metal and you have to do all the normal driver stuff yourself anyway.Statefulness: That an API design thing, I can see why they did it for backwards compatibility. Maybe they should have gone for a clean break
Extensions: Yep, that a problem.
Vertex buffers: Reading this it sound like display lists would be a better fit for this.
Render to texture: Got to agree with you on this, the windowing system intergration is a pain, the ARB seem to agree with ES only having EGL not a lib per windowing system.
Codepaths: Having been given the lucky job of making a render engine work with a lot of D3D drivers. We had many code paths working around missing feature or buggy drivers, so I don't think making any app work on a broad spectrum of cards is not simple or easy.
Very true, you do have the software failbacks in D3D for everything, OpenGL will only have them for whatevers is in the core spec for that version.
I was not trying to be pro OpenGL, it has it own problems, new stuff taking an age to be added to the core being at the e top of them, but the ARB has been working much faster in the last year/18 months. Hopefully they can keep moving things on.
In D3D you need to check caps bits for feature, OpenGL you need to check if the extension is supported, seems about the same to me.
I don't understand your comment about OpenGL being Stateful, D3D also stores its own internal state and it maybe more than one copy, one for the DX runtime and another in the driver proper.
About the extensions, nothing stops a Radeon (or anyone else) implementing the NVidia extension (which I think they do). OpenGL allows you just to call the new features (if supported). In D3D access the new feature means you will need to move all your calls to the new interface.
Vertex Arrays do the same sort of job as Vertex Buffers in D3D, plus you have display lists so you can combine geometry and state change into a single call.
In the end to support cards with different features sets you are still going to have different codepaths.
Link to a torrent of interview as an MP3.
AMD have had dual core chips on the roadmap for sometime (I know not the same as SMT/HyperThreading), they will also add SSE3 at the same time. Do Intel have the on chip memory contoller? or the Glueless 4 Way systems?
The Windows DDK also uses AMD64
Not having any clear gains is not stopping the UK Government steamrolling ID cards onto the statute books. See Stand.
We don't want him either, maybe try Iraq?
Only the US now, they stopped selling them sometime this year in the UK. Have a look at this