Jump to content

Invisible Cockpit


Airic

Recommended Posts

Hi Folks!

I have a nasty bug here!

As you can see on the screen shots the cockpit becomes particially invisible. I happends especially when I fire the cannon, or when I look sideways out auf the canopy.

Sometimes it happens ever without any reason. Depends on the zoom and view angle.

 

Is there anybody with the same problem or even with a solution?

Would be great if you can help me there!:thumbup:

 

If it helps, my system specs are:

Vista 32, Geforce 6600, 2GB ram

Latest Geforce Diver: 100.65 Forceware

 

PS.: As mentioned in a other thread, I tried to set my visible rage settings to low, medium and high, but still got the same prob. in each setting.

ScreenShot_000.thumb.jpg.e69548a36ec9b8578522a7ee560cd185.jpg

ScreenShot_001.thumb.jpg.3a19ca9d5baa081a0aa2b2265d7832d6.jpg

ScreenShot_002.thumb.jpg.cdc418d7a8866f1cae6e03335e23857d.jpg

ScreenShot_003.thumb.jpg.f1898b667af3bcad920de54b44196392.jpg

Link to comment
Share on other sites

Thanks for your fast reply!:thumbup:

 

I figured out that at the start of a mission everything is fine, but it gets worse when any actions take place like shooting ground targets or planes, or when i got shoot at.

When I take damage the cockpit stays like shown in the

screen-shots in any zoom or view angle and doesn't come back to normal.:mad:

Thats pretty annoying since Lock-on is such a nice looking sim!:cry:

 

By the way, i have FC 1.12a installed but i had the same prob in Lock-on 1.02. I hoped so much that after patching this prob will disapear, but it didn't!

 

Any idea how to fix it?:helpsmilie:

Link to comment
Share on other sites

Not only the video driver could be the issue but i had the same problem when i put Vista on. I found that part of the problem was DX10.

 

You should install a earlier version of DX along with video driver. That should help out.

=RvE=Atomic

 

Alienware Area-51, Intel Core2 Quad CPU Q9400 @ 3.2GHz, 8gig Corsair XMS2 DDR2 Ram, EVGA SC GTX 570, Western Digital 1.0TB 64mb cache HD. Windows 7 Ultimate 64, Saitek X52 & Saitek Pro Peddals, TrackIR 4 Pro with Track Clip Pro.

[sIGPIC][/sIGPIC]

Link to comment
Share on other sites

Mebbe you were in stealth mode. ;)

 

Just kidding man, hope you get it cleared up. :)

---------------------

 

FX 55 Sandy@ 3.03 GHz

Tuniq Tower 120

DFI Lanparty CFX 3200-DR/G

(2X) X1950XTX Crossfire@ 695 core

2048 OCZ PC 3200 Platinum (2-3-2-5)

Antec TP3 650

Samsung 19" LCD (8ms)

Saitek X-45 HOTAS

Track IR 4

CH Pro Pedals

:pilotfly:

Link to comment
Share on other sites

Ok, DX10 isn't the problem, because i have 9.0c installed.

I also downloaded and installed the beta drivers but they didn't help either.

 

By searching the forum I discovered a nice tool: LoCFG

(Thanks for the guys who made that, great work!:thumbup: )

 

I messed a bit around with the settings,

and it seems like the "middle clipping" MUST be the same value as the

"near clipping" to get rid of the problem!

 

Low "near clipping" values looks better but too small "middle clipping" values causes an other nasty graphical disorder.

So I set both to 1.0 and it works fine for me.:smartass:

Link to comment
Share on other sites

Ok, DX10 isn't the problem, because i have 9.0c installed.

I also downloaded and installed the beta drivers but they didn't help either.

 

By searching the forum I discovered a nice tool: LoCFG

(Thanks for the guys who made that, great work!:thumbup: )

 

I messed a bit around with the settings,

and it seems like the "middle clipping" MUST be the same value as the

"near clipping" to get rid of the problem!

 

Low "near clipping" values looks better but too small "middle clipping" values causes an other nasty graphical disorder.

So I set both to 1.0 and it works fine for me.:smartass:

 

Just a foolish question. How did you get 9.0c installed instead of dx10? I thought Vista installs dx10 when you install Vista. I think Hitman would like to know the answer to that question. Hope you can help.

Link to comment
Share on other sites

Ah, yes! You are right! It's DX 10!:doh:

Sorry for that.

 

Because i was asked from the install routine of an other game to install

DX 9.0c (and did so) i thought i have DX 9.0c installed.

My fault, just looked, its DX10.:music_whistling:

Link to comment
Share on other sites

Here is your answer about DirectX 10 its straight from "help" in Vista.

 

 

At a minimum on this version of Windows, you have DirectX 10....

 

 

Can I uninstall DirectX? No. It's an integral part of the Windows operating system and cannot be removed.

The code is probaly in Russian anyway.
Link to comment
Share on other sites

 

PS.: As mentioned in a other thread, I tried to set my visible rage settings to low, medium and high, but still got the same prob. in each setting.

I dont understand why this didnt work, cuz I have the same problem and setting the visible range took care of it. I should ask what version of LockOn are you running...but would it matter?

Link to comment
Share on other sites

YEA! :pilotfly:

101.41 Forceware works fine for me! THX!:thumbup:

Problem solved! :D

 

 

@ hitman 214th: I have FC 1.12a. I found out that i had to change "near clipping" and "middle clipping to the same value: 1.0

Low visible range setting does this, but i didn't wont to play in low settings.:smilewink:

 

In middle and high default setting the "near clipping" value is 0.2 and "middle clipping" is 4.0, so it didn't work for me.

I had to change both settings to 1.0 to get rid of this bug.

 

The new beta Forceware 101.41 even works with the default settings, so everything is fine!:thumbup:

Link to comment
Share on other sites

  • Recently Browsing   0 members

    • No registered users viewing this page.
×
×
  • Create New...