• We have updated our Community Code of Conduct. Please read through the new rules for the forum that are an integral part of Paradox Interactive’s User Agreement.
As I said I take you at your word.
Let's let the matter drop before the Mod of this place bans us both. ;)
 
haha,
I did also beleive you the first time :)

Anyway back to the topic: Using the dxdiag, to set refresh rate worked. I have not seen any problems so far. Though the quality is extremly bad, compared to the tv-out of my new ATI card. Thank God I bought the new card. :cool:
 
Well what did you set it at?
 
Both my monitor and the tv is set to run 75 hz, dx is also set to that. I didn't try and go higher. Though I think the TV can go op to 100 hz.

Not that it matters I shouldn't be able to see the differance so high up. but still the flickering is gone.
 
Then you must have an extremely advanced piece of TV technology.

Mine knows only of two types of input frequencies: (bought it this year, 16x9 widescreen model)

PAL: 625 scan lines, 50 Hz (interlaced)
NTSC: 525 scan lines, 60 Hz (interlaced)
SECAM (don't know exact specs, but it displays as PAL in black and white)

Anything I hook up to it (PC with TV out, DVD player, VHS player, etc) must conform it's signal to one of these, or the screen goes blue/black.

Jan Peter
 
Last edited:
I actually didn't know that, so I just tested it, you are correct, the digital tv runs at 60hz. So it seems there is a bug in the driver, or a feature if you want to call it that. ;)

DirectX is set to 75
Monitor is set to 75
No matter what I set the digital tv to its 60 hz displayed.

But its working....

EDIT: I can actually set the tv to run 200 hz, and its still at 60. Hence I can confirm its a gfx driver og MS bug, I am thinking the latter :D

Anyway doing some more testing, I found that setting dx and monitor rate to the same everytime, its works fine. Why the *bip* is that?
 
Last edited:
Did anyone manage to figure this out?

This difficulty (I won't call it a bug, yet) is my primary annoyance with EU2 (well, besides the A(un)I :D ). It happens about once every 4 times I quit the game, and I have never been able to duplicate any particular in-game activity that affects the occurrence of this situation.

I don't run anything fancy. I have an HP Pavilion 6830 with Windows Me 4.90 (Build 3000). It has the simple Intel 82810 Graphics Controller built into the system originally; I don't use a graphics card. I run the very plain vanilla HP Pavillion mx50 CRT monitor at 1024 x 768. DirectX 9.0c is my current version of that software, but I've had others along the way. I don't remember for certain when I first started having trouble with the resolution upon exiting the game.

It is quite annoying to have to restart your computer after exiting the game in order to run the game, or any other game, or anything else using DirectX. I find myself saying a little prayer each time I exit the game, hoping that I'll get the familiar "click" sound and a proper looking screen.

Since this is the only game that I have used (and I'm not exactly a game novice ;) ) that has this trouble, it is clear that it is a game-related issue. Solving it would make my day quite complete. :)
 
If you read the thread you cannot really make that assumtion.

Try renameing the AVI folder to AVI_back, that has helped reduce the frequency for some.