Continuum issues on x64 systems

[»Ceiu]

I tested this stupid game on the 64-bit edition of XP and naturally it didn't work like it should. Most things were ok, but:

 

(1) The goddamn engine sound would not stay off. Every time you entered the game you had to shut it off.

(2) The Alt, Ctrl and Shift buttons could not be used at all in-game. The exception is in spectator mode where holding shift makes the screen scroll around quicker (which probably isn't Priit's code, as it disregards the input config entirely).

 

There's probably more, but who cares? #2 makes the game unplayable without some very goofy key configurations, and #1 was driving me batshit insane every time I was testing a possible solution to #1.

 

I don't expect this to be fixed as it's a client issue... but maybe this will save someone else the trouble of trying to figure out what's going on.

 

-C

[»doc flabby]

I tested this stupid game on the 64-bit edition of XP and naturally it didn't work like it should. Most things were ok, but:

 

(1) The goddamn engine sound would not stay off. Every time you entered the game you had to shut it off.

(2) The Alt, Ctrl and Shift buttons could not be used at all in-game. The exception is in spectator mode where holding shift makes the screen scroll around quicker (which probably isn't Priit's code, as it disregards the input config entirely).

 

There's probably more, but who cares? #2 makes the game unplayable without some very goofy key configurations, and #1 was driving me batshit insane every time I was testing a possible solution to #1.

 

I don't expect this to be fixed as it's a client issue... but maybe this will save someone else the trouble of trying to figure out what's going on.

 

-C

1. I have this problem in 32-bit XP, it started fairly recently an I have no idea why.

2. It doesn't suffer from these problems in 64-bit Vista which is a much better operating system for 64-bit work (which gives you an idea of how terrible 64-bit XP is, its basically a hack of Windows 2003 64-bit edition)

Edited May 22, 2009 by doc flabby

[Samapico]

Problem 1 is a known issue, on both 32 and 64 bit systems. Doesn't always happen though

 

Possible solution is ?sound=1\?sound=0 in auto commands

[CRe]

Try changing key defs in options.

[»Ceiu]

1. I have this problem in 32-bit XP, it started fairly recently an I have no idea why.

2. It doesn't suffer from these problems in 64-bit Vista which is a much better operating system for 64-bit work (which gives you an idea of how terrible 64-bit XP is, its basically a hack of Windows 2003 64-bit edition)

 

Problem #1 doesn't bother me so much, as the game is still playable. The real issue here is #2; which cannot be fixed by simply reassigning keys (unless I feel like learning a whole new set of keys, which I don't). I can assign them fine in the input config; they just don't work in game, which pisses me off.

 

Regarding the comment about 64bit XP... No. Just... no. The problem here isn't XP, nor will it ever be. This keyboard works fine in every other program and on several other systems. The problem is entirely with Continuum; which, as we all know, is coded mostly like shit.

[Deathmonger]

I run Continuumm on XP x64 just fine, although I have remapped my keys. Ctrl/Alt/Shift work fine. I've noticed Win 64 is fairly sensitive to being run on certified compatible hardware.

[rootbear75]

whats the actual difference between x32 and x64?

i could never figure it out

[Samapico]

32bit vs 64bit memory

 

with 32bits, you can go up to around 4 000 000 000, which, in terms of memory, would be 4GB. This means with a 32bits system, you can only address up to 4GB of memory, which is why many systems have a limit of 4GB RAM. With 64 bits, the limit would be... 16x10^18 or something.

The system basically works with chunks of 64bits instead of 32bits, which mean data can be passed on faster.

The OS itself has 2 different versions, because pretty much all functions can be re-made more efficiently with 64bits.

 

This is probably not exactly right, but that's the main idea I guess.

Wikipedia could probably answer you better.

[rootbear75]

With 64 bits, the limit would be... 16x10^18 or something.

to answer your question:

16.8 million terabyte

[L.C.]

whats the actual difference between x32 and x64?

It's x86 and x64. These refer to architectures, not bits.

 

The emergence of the 64-bit architecture effectively increases the memory ceiling to 2⁶⁴ addresses, equivalent to approximately 17.2 billion gigabytes, 16.8 million terabytes, or 16 exabytes of RAM. To put this in perspective, in the days when 4 MB of main memory was commonplace, the maximum memory ceiling of 2³² addresses was about 1,000 times larger than typical memory configurations. Today, when over 2 GB of main memory is common, the ceiling of 2⁶⁴ addresses is about ten trillion times larger, i.e., ten billion times more headroom than the 2³² case.

But rootbear75 has already answered the question.

 

http://en.wikipedia.org/wiki/64-bit#History

[Samapico]

Oh, I wasn't understanding that quote at all with the 232 and 264 until I realized they were supposed to be superscript lol (fixed)

[»Lynx]

whats the actual difference between x32 and x64?

It's x86 and x64. These refer to architectures, not bits.

 

No, x64 (in this thread) is referring to Windows 64 bit, where as the architecture is x86-64. If we were referring to a 16 bit system, it'd be x86-16, provided it's under the x86 processor architecture, which isn't the only architecture, just the most popular. So, if anything - root, it's 32bit and 64bit. Anywho, XP64 is terribad, however it is entirely a client issue as I'm sure that the client wasn't compiled with WoW64 in mind. You should be prepared for compatibility issues whenever changing architecture. The game runs, just runs badly. Same goes for Linux, and Mac. As I understand it, the translation is done better on Vista, but I'd expect it to still be shit.

 

-L