the problem shown in the thread was not my problem cause i got intel mainbord an the new drivers but the forum showed my another problem that was mine
you will start roll on laughing.
you have to change the power settings for the kernel from normal to high performance so that you wont freeze :0f:and that after 10 years of windows .
and i also changed the power settings for the internet option so that windows never ever can send the internet control to sleep that also may also caused the problems
I knew why i always call it windoof (doof germ for stupid)
your CPU cern- kernel shown in all the forums needs power and this system tries to use as less power as possible. in my case too less so the cern didnt get enough and crashed freak system- now it workes
just set from "standart" to high performance
BUT : FH2.2 looks different the weapons look sharper and they are farer away then in xp
for example: when you hold the garand you can see till the iron sights
now: you can see the end where the metal part meets the wood
deutsch: man kann vom verschluss ende bis zum anfang des holzgriffes sehen auch ist die kimme/korn weiter weg.
Hey Irish bevor du den BF2 1.5 Patch installierst muß der 1.41 Patch installiert sein!
Hier die korrekte Reihenfolge
BF2 Original installieren
dann den Patch 1.41 für BF2
danach den 1.5 für BF2
Jetzt FH2 Version 2.2 (Falls vorhanden sollte 2.15 deinstalliert werden)
Ich bin auch sehr interessiert an Windoof 7 währe cool wenn du in ein paar Tage/wochen Fazit ziehen würdest.
Bekommst von mir Virtuell auch ein Bier spendiert. :0m:
i think it's the widescreen resolution, causing a wrong fov (field of view).
There are many games that do not support widescreen properly. These games usually let you set a widescreen resolution, but do not adjust the field of view (FOV) accordingly. This causes the top and bottom of the screen to be cropped. Because of this issue, I decided to develop a program that will adjust the field of view for the aspect ratio of your monitor.
I don't know what the fixer does really. The page just described the issue (googled fov and bf2) and I know that a wrong fov often results in the problem in question.