[RedruM-X]

Anyone know a solution please I really want to play this game.

I installed Gothic 3 + cp1.72 (also tried 1.60) and the game runs at 10 times the speed it is supposed to, so 10 times TOO FAST.

:S

I don't understand this, I couldn't find a solution on the internet for this so maybe someone here knows a solution ?

When the game starts (actually the whole time), with the village in the battle where you get the help screen saying press 1 to draw your sword, everything is sooo fast, I tried changing settings etc, but everything is on highest settings /high quality so I cant get it too run any slower ...
I even tried minimizing the game and then in task manager running on only 1 cpu and it stays the same.

It's like running an old game on a core2duo, that kind of problem, but seeing this game is made to use c2d it's not that either.

After finishing the battle I can clearly see that the game is running way too fast because the day/night cycle is fast and also the animations of everything run really fast, it looks like my char has nervous ticks or something because of it. When I walk (read : run bloody fast) I can see it too, it's like there is a hidden option which lets the game run really fast :-S.

Vsync on or off no difference.

:-S

I really want to play this game.

I have a C2D E6700 2.67 oc'ed at 3.6Gz with a GTX 260


Anyone any ideas please ?

[Larisa]

Known problem, although usually it happens with AMD x2 processors:

Solution: http://forum.worldofplayers.de/forum...9&#post2506569

Btw: Welcome here

[RedruM-X]

Tx for the welcome.

But sorry this is not a known problem and what you suggested is totally beside the problem.

First of all, the hotfix for XP is for SP2, I have SP3.
Second of all hotfix won't help, neither will putting the game on 1 cpu will help.

I actually discovered it's because of the game itself, which makes a faulty detection in speed somehwere.

My CPU atm is overclocked to 3.64 Ghz, while standard it is a 2.67Ghz core2duo E6700.

I went back to my old settings in bios and set the speed back to 2.67Ghz, I started the game and then everything is at normal speed. This without doing anything else but those changes !

So the problem lies somewhere when you start the game and it detects your cpuspeed or something.
Anyone know of any shortcut addons like gothic3.exe -cpuspeed=3640 or something ?

As the above mentioned solution is totally not what my problem is.

It's not only the day/night cycle but everything which runs too fast.
100% sure now it's the game which wrongly detects my cpuspeed. It sets up the game as if I was running a 2.67 and ofcourse when the scripting and everything else suddenly runs at 3.64Ghz it all goes too fast.

Anyone any solution ?

[RedruM-X]

To give you more insight, I'm not the only one having had this problem it seems :

http://forums.guru3d.com/showthread....=1#post3309490



I don't want to go downclock my cpu everytime I want to play this game, this means reboot every time just for one game ... would be too ridiculous

:'(

If anyone can help please.

Can't I somewhere say in ini's which CPU speed I exactly got etc or in the shortcut of the game (-cpuspeed=3640)

[Larisa]

So the problem lies somewhere when you start the game and it detects your cpuspeed or something.
Anyone know of any shortcut addons like gothic3.exe -cpuspeed=3640 or something ?

As the above mentioned solution is totally not what my problem is.

It's not only the day/night cycle but everything which runs too fast.
100% sure now it's the game which wrongly detects my cpuspeed. It sets up the game as if I was running a 2.67 and ofcourse when the scripting and everything else suddenly runs at 3.64Ghz it all goes too fast.

Anyone any solution ?

I'm not sure how modern games deal with cpu cycles, detecting time, etc., but that with increasing/decreasing the cpu speed is from the DOS days.

And, overclocking isn't always safe, especially when you jump a certain limit.
There can be other errors, depending on what part of hardware you overclock. That's why benchmarks must be run in the process of overclocking, to detect that limit.

Edit:

I don't want to go downclock my cpu everytime I want to play this game, this means reboot every time just for one game ... would be too ridiculous

Others went to much greater troubles to make the game run, a reboot each time you want to play seems a minor inconvenience to me. But that's just me.

And:

I have a core2duo E6700, standard clocked at 2.67Ghz, and I oc'ed it to 3.64Ghz (totally stable).

Looks like it isn't totally stable, is it?

[RedruM-X]

Looks like it isn't totally stable, is it?

LOL
Why, because the game messes up it's detection ?

Sorry but I play games without any problem, hours on end :

Call of Duty 4 & 5
WoW
Unreal Tournament 99
Unreal Tournament 2004
Unreal Tournament 3
Settlers 6
Street Fighter 4
Fallout 3
And many, many others including Oblivion and many other RPG's (like gothic 2).

I've played tons of games with those oc's, and those overclocks you don't get by not knowing anything about it, you don't just put it on that speed in one time. I've been overclocking pc's for years now and what you are suggesting is ridiculous, this problem has nothing to do with a stable overclock or not.

Going back to stock speed showed that the cpu speed detection of this game is buggered so ...
Has nothing to do with overclocking, all to do with the game.

OC is 100% stable, there are many heavier games for ones sustem out then this tbh.
And tbh I've probably run more benches then you ever will, but just to name a few : Orthos / LinX / p95 / superPi / OCCT

Sounds like you have no idea about overclocking when you said it's dangerous, it's only dangerous for people who don't know what they do and don't know how to cool their machine, aka, you.
So Replies like that don't help.

If I don't get any replies, then fine, but replies like that saying my oc is not stable don't make sense at all. If my game would've crashed or whatever then maybe you'd be right, just maybe.

The problem is the detection the game uses, simple as that.

Ty

[WernerTWC]

Has nothing to do with overclocking, all to do with the game.

I have played g3 on overclocked hardware without any problems.

What exactly do you have overclocked and how?

Sounds like you have no idea about overclocking when you said it's dangerous, it's only dangerous for people who don't know what they do and don't know how to cool their machine, aka, you.
So Replies like that don't help.

Replies like hers helps to exclude some possible error-sources, if you answer to everyone who wants to help you in such a unfriendly way, you shoudn't wonder when the answers getting fewer.

Btw.: WELCOME BACK, Larisa!

[DTR]

Applications are not synchronized by cycle counts.
There is a high resolution timer on board every semi-modern computer that is used for that.

And VSYNC just causes the dx device to wait out for the monitor retrace in order to avoid tearing artifacts in the image. Should rarely be an issue...

[Larisa]

The problem is the detection the game uses, simple as that.

As far as I know, there isn't a command line or ini setting to tell the game the CPU speed.
If you like, you could do a little experiment and tell us exactly at what cpu frequency the game starts to run faster, increase the speed in small increments, maybe there's a threshold.


But I'm still glad you can play the game, if you really want that.

Btw.: WELCOME BACK, Larisa!

It's good to be back

[Rocket]

http://forum.jowood.com/archive/index.php/t-163101.html

Nameless2
08-05-2009, 20:07
Alright, in that case it seems to be an overclocking issue indeed. Have you tried overclocking with a 'natural frequency' on the frontside bus?
Instead of 389MHz take something like 266 or 333 and make sure the multiplier for the RAM is still making it to 533, 667 or 800 (or 1066 or 1200) in that case. See what happens then.

yahourtnature
10-05-2009, 18:28
Good one, Nameless2, that's simply it Effectively the game seems to need a "standard" FSB like 266, 333...

Post back if it works.

[RedruM-X]

I already said that putting fsb on a "natural" or lower one works, I found it out myself if you read my post before, and it's something which I'm not going to do, not going to change my fsb speed every time I want to play one game, I play games in shorter periods and play at least 4 or 5 different a day, and since I play Unreal for a clan we sometimes just suddenly decide to play, that would mean that when I'm playing Gothic 3 with normal fsb I would have to reboot every time for a game, then after that game if I want to jump right back in to Gothic 3 I would have to reboot again, and so on and so on, that is a no go.

Thank you though.

It's a pity, seemed like a very nice game, but passing on it now.

Risen has the exact same problem btw.

And things like that are very abnormal for a game, these are the only games I've seen doing that.

Bye