Follow along with the video below to see how to install our site as a web app on your home screen.
Note: This feature may not be available in some browsers.
BBA said:64 bit Vista DX10 multithreaded games have my vote going forward.
I'm not a programer.... but I've read that the big problem taking full advantage of the new Xbox and PS3 is that type of programing is a nightmare.penguin said:I vote multithreaded
Kendrak said:I'm not a programer.... but I've read that the big problem taking full advantage of the new Xbox and PS3 is that type of programing is a nightmare.
Digital Viper-X- said:I don't see why multithreading a game would be a programming nightmare , im only done my first year inprogramming though o.0 so who knows
Mine to.BBA said:64 bit Vista DX10 multithreaded games have my vote going forward.
so running in 64-bit mode doesn't allow the CPU to add 2 64-bit numbers as one instruction rather than two?LordBritish said:64 bit games will only allow more memory use - beyond 4gb.
That's it folks.
64 bit games does not mean more speed. Some 64 bit applications actually run slower than their 32 bit counterparts..
People with a single core CPU will so see no benefit from multi-threaded games either.
drizzt81 said:so running in 64-bit mode doesn't allow the CPU to add 2 64-bit numbers as one instruction rather than two?
Yes you are. Really big numbers have to be broken up into multiple tasks since they can not fit in the register space.LordBritish said:Adding 2 numbers has always been a single instruction - even in the 16 bit days. Am I missing something here?
ok, i am not sure how to word it:LordBritish said:Adding 2 numbers has always been a single instruction - even in the 16 bit days. Am I missing something here?
vortexpud said:Far Cry in 64 bit mode is pretty![]()
drizzt81 said:ok, i am not sure how to word it:
The number of instructions cycles for a ADD command depends on the size of the two operands as well as their location (register etc.). Considering that a 64-bit operand does not fit into a 32-bit size register, one could consider that such an operation would be faster on a 64-bit arch.
Least said:Multithreaded games would benefit more than 64 bit, for sure.
Multithreaded programming is a bitch. It is extremely hard to write good code for. Viper, what language are you using? Java does not have real threads (I am taking a guess this is what you're learning considering the trend in colleges and high schools). Multithreaded programs will often have 'shared resources' that both threads will eventually have to access. They cannot be accessing it at the same time. More problems involved with the timing of the threads. etc. etc. etc.
umm, but yeah. let's see some multithreaded games!![]()
Not if you are dealing with intergers.LordBritish said:I understand that but that does not equate to faster applications - just more precise numbers.
LordBritish said:If you think about it, a GPU and a CPU is sort of like multi threading![]()
drizzt81 said:ok, i am not sure how to word it:
The number of instructions cycles for a ADD command depends on the size of the two operands as well as their location (register etc.). Considering that a 64-bit operand does not fit into a 32-bit size register, one could consider that such an operation would be faster on a 64-bit arch.
you're missing one VERY important thing:LordBritish said:64 bit games will only allow more memory use - beyond 4gb.
That's it folks.
64 bit games does not mean more speed. Some 64 bit applications actually run slower than their 32 bit counterparts..
People with a single core CPU will so see no benefit from multi-threaded games either.
(cf)Eclipse said:you're missing one VERY important thing:
x86-64 doubles the number of integer registers (along with a few other things). that alone should lend itself to a reasonable boost in performance if properly optimized for.![]()
(cf)Eclipse said:you're missing one VERY important thing:
x86-64 doubles the number of integer registers (along with a few other things). that alone should lend itself to a reasonable boost in performance if properly optimized for.![]()
Sabrewulf165 said:Why not games that are 64-bit *AND* multi-threaded![]()
Anarchist4000 said:Ok gonna clear a few things up here. Multithreaded would be much faster, given more than one core for processing. 64bit would just make things larger, more accurate. A 64 bit CPU will do almost nothing for the performance in games.
I might be wrong but my understanding of the x86-64 CPUs was that they do nothing but 32 bit processing. They can however address 64 bits worth of data. And typically you don't do any processing on address registers in very many programs. So you are doing 32 bit math but have in excess of 4GB of ram that you can use. This is more relevant to systems that have a bunch of stuff running at once. While your game might only use 2gb of ram you could have windows and a bunch of other programs still using in excess of 2gb of ram without any major worry. Still using 4gb of ram is a task in itself.
Also with multithreading I don't see why everyone thinks it's that hard to implement. Any decent programmer should know how to do it fairly efficiently. The trick is to just do everything in batches. Also there is nothing wrong with threads accessing the same data at the same time. They just can't be changing that data. So if you had 32 integers and 4 threads doing nothing but summing them all up independently of eachother there would be no problems at all. Typically for multithreading you'd just have one main thread running and split to several when you came upon some data processing or numbers to be crunched.
Also with the numbers of threads being used in games those numbers can be somewhat deceiving. Typically you'd have 1 thread for each seperate network connection that existed. As well as other threads that typically do nothing more than sit there and wait for something to happen.
Anarchist4000 said:Also with multithreading I don't see why everyone thinks it's that hard to implement. Any decent programmer should know how to do it fairly efficiently. The trick is to just do everything in batches. Also there is nothing wrong with threads accessing the same data at the same time. They just can't be changing that data. So if you had 32 integers and 4 threads doing nothing but summing them all up independently of eachother there would be no problems at all.
Anarchist4000 said:Also with multithreading I don't see why everyone thinks it's that hard to implement. Any decent programmer should know how to do it fairly efficiently.
The trick is to just do everything in batches. Also there is nothing wrong with threads accessing the same data at the same time. They just can't be changing that data. So if you had 32 integers and 4 threads doing nothing but summing them all up independently of eachother there would be no problems at all.
Typically for multithreading you'd just have one main thread running and split to several when you came upon some data processing or numbers to be crunched.