Framerate locking IS common... because on the console with set hardware you can optimize to hit one specific framerate...... and then when you port to the PC you need to keep the framerate locked (or have a REALLY painful porting process) because of all the assumptions you made making the console version assuming the framerate will always be 30 fps (like with Gametime, etc)
Just about every console port doesn't have the resolution locked.... that said their internal assets are usually low-res enough that the extra resolution will just be rendering the crappy artwork with even more crappy detail.
They wouldn't matter without extra resolution to display that extra detail... assuming of course that the input detail is equal or greater than the output detail the screen resolution allows.
And while Real-Time Ray Tracing is the "Holy Grail" and is achievable, there is no way VRAM is going away to be replaced with traditional CPU memory. There are so many memory optimizations in the rendering pipeline that it would be stupid to suggest that it all should be tossed out and use slow DRAM instead.
He was actually talking about something like CUDA or OpenCL programs that look similar to a typical software rendering engine.
GPUs would still be there... but you would "talk to them" in a similar way you would a CPU. Only with slightly more simple commands that are parallelized across thousands of cores.
Basically Tim Sweeney is annoyed at all the DirectX and OpenGL quirks they need to dodge and would want to program each engine basically from first principles -- but still use the GPU for calculations that could be split into hundreds or thousands of independent parts.
Eh... the consoles are slightly more memory bound than anything.
As for rendering at 720p? That's generous... many of the blockbusters render at lower (some much lower) than that.
And if the security measures really helped... I'm sure there'd be more support.
There's a balance between security and convenience/performance/freedom in whatever we do. Many people have many different lines they draw -- regardless of where you draw your line... you need to be efficient at getting the most of the former for the least of the latter.
I mean hey -- easy way to solve this problem: ban flying. No airplane problems then.
Mind the double post... but I am with on you moving to Linux... but not so much for what Microsoft doesn't let you install (because they're not toooo bad about that) -- but more for what you're allowed to do in the future for backwards compatibility or other long-term maintenance that's required on source that's proprietary to Microsoft.
Uh, I have no problems registering DLLs as they're required for various other applications...
1) You made sure that you right-clicked on CMD and ran as administrator?
2) You made sure that CMD's in the PHP directory, with php5activescript.dll in that directory?
3) You made sure to type:
Maybe content companies will realize that DRM simply doesn't work... especially not when compared to the benefits of being smart with their business models.
One reason is because they're dependent on higher-permissions code... which the exploiting code pretends it is by over-writing part of the higher-permission code in memory... such that the next time said code is run, it is no longer there.
That's actually how DEP works... the CPU executes a string of commands... one after another... some from memory, some from cache, some jumps, some sequential...... then when it sees code marked as "data"... it freaks out and realizes it somehow got misdirected out of "execute" and fell in a data buffer. If DEP wasn't enabled... it wouldn't check to see where it is and would just run it with whatever permissions SHOULD be there. If DEP was enabled... the CPU freak-out would force an instant crash and signal Windows that (x) was terminated because it tried to execute data.
The reason why executing data is dangerous is because it's a section of memory that the programmer said "this should not contain any code... and can be written to by someone other than me".
Which by the way is how jailbreaking Apple products works... you're installing malware on the system to get a higher permission level than the application wishes you to have. The same process you used to usurp admin rights from Apple on your phone is the same process anyone else needs to do to usurp admin rights from Apple on your phone... which is exactly how viruses are made.
Simply put... it's ridiculously hard to write secure code. All you can do is reduce how much access to elevated permission code you have... and fix any errors as you, or someone, finds them.
I think the bigger story is that after all these iterations... developers still don't know how to properly use the hardware.
People envision that Kinect will be used for sign language recognition and creating custom animations/taunts (actually waving bye to that Pyro wanker's head).
Will we ever see a developer use the hardware? Or will they just use it shallowly and default to what they know for anything of substance?
Well to be fair you can get a 640x480 webcam-quality recorder shaped like a car starter for approximately 15$... so it's not like this level of surveillance wasn't possible until now......
But it does make me cringe to think about gifts from creepy stepfathers.
Slashdot Mirror
Framerate locking IS common... because on the console with set hardware you can optimize to hit one specific framerate... ... and then when you port to the PC you need to keep the framerate locked (or have a REALLY painful porting process) because of all the assumptions you made making the console version assuming the framerate will always be 30 fps (like with Gametime, etc)
Wii was actually one of the only consoles to NOT be sold at a loss.
2006 Article
Just about every console port doesn't have the resolution locked. ... that said their internal assets are usually low-res enough that the extra resolution will just be rendering the crappy artwork with even more crappy detail.
Its not all about resolution.
What about polygon count, and memory size?
They wouldn't matter without extra resolution to display that extra detail... assuming of course that the input detail is equal or greater than the output detail the screen resolution allows.
They must of been drinking the same, with all due respect to an otherwise extremely bright programmer, software rendering kool-aid as Tim Sweeney.
"The End of the GPU Roadmap" http://graphics.cs.williams.edu/archive/SweeneyHPG2009/TimHPG2009.pdf
And while Real-Time Ray Tracing is the "Holy Grail" and is achievable, there is no way VRAM is going away to be replaced with traditional CPU memory. There are so many memory optimizations in the rendering pipeline that it would be stupid to suggest that it all should be tossed out and use slow DRAM instead.
He was actually talking about something like CUDA or OpenCL programs that look similar to a typical software rendering engine.
GPUs would still be there... but you would "talk to them" in a similar way you would a CPU. Only with slightly more simple commands that are parallelized across thousands of cores.
Basically Tim Sweeney is annoyed at all the DirectX and OpenGL quirks they need to dodge and would want to program each engine basically from first principles -- but still use the GPU for calculations that could be split into hundreds or thousands of independent parts.
Eh... the consoles are slightly more memory bound than anything. As for rendering at 720p? That's generous... many of the blockbusters render at lower (some much lower) than that.
Yet every iPhone susceptible to that exposure could be updated within 2 weeks. I would like to see Android pull that one off...
If Apple gets around to it, of course.
They've been known to let vulnerabilities go until they can roll them all up into a nice 250MB-or-so patch.
Hey, what's the rush? They're not a target.
And this is why people who believe there aren't such things as "Defensive Patents" are wrong.
...
...
Sure... there SHOULDN'T be such things as defensive patents... but there are... to protect yourself from plagiarizing... vulching... trolls.
Because that would mean that their just released Facetime for Mac would be called Arsetime for Roadapples.
Nah, that was the project his team was supposed to spearhead.
Ugh, imagine that thing getting set off.
And if the security measures really helped... I'm sure there'd be more support. There's a balance between security and convenience/performance/freedom in whatever we do. Many people have many different lines they draw -- regardless of where you draw your line... you need to be efficient at getting the most of the former for the least of the latter. I mean hey -- easy way to solve this problem: ban flying. No airplane problems then.
Just another way Foxconn employees are giving to their company.
Mind the double post... but I am with on you moving to Linux... but not so much for what Microsoft doesn't let you install (because they're not toooo bad about that) -- but more for what you're allowed to do in the future for backwards compatibility or other long-term maintenance that's required on source that's proprietary to Microsoft.
Uh, I have no problems registering DLLs as they're required for various other applications...
1) You made sure that you right-clicked on CMD and ran as administrator?
2) You made sure that CMD's in the PHP directory, with php5activescript.dll in that directory?
3) You made sure to type:
regsvr32 php5activescript.dll
??
This post proves it. :-p
Maybe content companies will realize that DRM simply doesn't work... especially not when compared to the benefits of being smart with their business models.
Silly... there's no Iguanas in New York State... ... but you know I *love* my Soylent Green.
We're screwed.
There's a clap for that.
But... that's... tangential politics...
One reason is because they're dependent on higher-permissions code... which the exploiting code pretends it is by over-writing part of the higher-permission code in memory... such that the next time said code is run, it is no longer there.
... then when it sees code marked as "data"... it freaks out and realizes it somehow got misdirected out of "execute" and fell in a data buffer. If DEP wasn't enabled... it wouldn't check to see where it is and would just run it with whatever permissions SHOULD be there. If DEP was enabled... the CPU freak-out would force an instant crash and signal Windows that (x) was terminated because it tried to execute data.
That's actually how DEP works... the CPU executes a string of commands... one after another... some from memory, some from cache, some jumps, some sequential...
The reason why executing data is dangerous is because it's a section of memory that the programmer said "this should not contain any code... and can be written to by someone other than me".
Which by the way is how jailbreaking Apple products works... you're installing malware on the system to get a higher permission level than the application wishes you to have. The same process you used to usurp admin rights from Apple on your phone is the same process anyone else needs to do to usurp admin rights from Apple on your phone... which is exactly how viruses are made.
Simply put... it's ridiculously hard to write secure code. All you can do is reduce how much access to elevated permission code you have... and fix any errors as you, or someone, finds them.
Does that make me a fail or a win?... how about epicly in either direction?
I think the bigger story is that after all these iterations... developers still don't know how to properly use the hardware.
People envision that Kinect will be used for sign language recognition and creating custom animations/taunts (actually waving bye to that Pyro wanker's head).
Will we ever see a developer use the hardware? Or will they just use it shallowly and default to what they know for anything of substance?
Well to be fair you can get a 640x480 webcam-quality recorder shaped like a car starter for approximately 15$... so it's not like this level of surveillance wasn't possible until now... ...
But it does make me cringe to think about gifts from creepy stepfathers.