Some cards have problems with the effects.

As a matter of fact many effects (trails, explosions) ARE supported by my GF (mx):


but sometimes a particular effect is triggered (for example when I crash while in cockpit view)and immediatly I'm getting this :


I've read here that the fix is: put the effects to none. Yes it works perfectly well but this is not exactly the fix I am looking for......
A real fix would be UBI making a special effect file for low setting without the effects that are causing the blue screen. Or even they would fix this by reworking the file a little not a big deal.

Rather than telling us now that some card are not supported just for a few effects in the effects file!!! ???

This is the sim I bought and it is working very fine on my PC (lockon official webpage, FAQ):

What are Lock On's system specs?

Windows(r)98/ME/XP/2000
Pentium III 800/AMD Athlon 600 or better
256 MB RAM (512 MB RAM recommended)
3D video card (DirectX 8.1 compatible) w/32MB RAM (128MB recommended)
Sound Card (Direct 8.1 compatible)
DirectX 8.1 or higher (included on disc)
4X CD-ROM or better (Not recommended for use with CD-RWs)
Internet connection (56 kbps or better) or LAN for multiplayer
Hard Drive Space 1.1 GB

Return to Top

So please Mr UBI do something .

i've found this, posted by Clark in another thread here. Hope much it is untrue:

"According to Matt we won't see a fix for this, as non DX8.1 cards aren't supported"

It really depends.

Sometimes people know the causes of issues, sometimes they think they do.

It all comes down to how much "evidence" you can gather to prove or disprove. The worst that can happen is that you can waste time doing so, the best that can happen is that you find the real reason for a problem if it was initially incorrect.

If you can find out exactly what effect is triggering this blue screen, then you can ask people with supported cards to test and compile results.

From there you check for any anomilies in the results - these indicate that there is SOMETHING different going on there. Once you find out what is different and it's effect you can often narrow down the cause to something easily locatable.

Well, I've norrowed it down on my system. The effect that causes the blue screen of death for me is the Exhaust Blur effect. Everything else works fine.

If I turn on the blurring, when the aircraft slows to around 500KMH and the blur comes on, bam, blue screen. Never fails.

I'm running a 2.4GHz Pentium, 1GB of RAM and a GeForce Ti4600 128 MB card.

Funning thing is that the blur effect works fine on the SU33. Everything else...BSOD!

Bananimal I have the blur effect on off from the beginning but apparently when something is going wrong graphically in this game, it is always turning on blue

Bard I'm not going to spend much time on this myself this problem is recognized and should find a solution in the patch, ie exclude at least the effects that are causing this for the "low" effects. Would be a minimum.

But if somebody has a solution now I'm much interested, I've tried to open the effects file but it's beyong my own ability

well, since the blurr effects are a single item that can be ticked off in the options, it doesn't need fixing.

maybe if the sim enforced this being off if the hardware won't support it it would "solve" the issue of users not being configured "correctly".

I too have a geforce MX 440 (gonna be getting a Ti-4200 REAL SOON NOW!!!) and I too have this problem. I find that is caused when something, either a plane or missle or whatever, crashes into the water.

this is exactly what I mean when I'm telling that the "Low" effects settings in the patch should be modified to exclude any of the not supported effects that are causing this. This would be the logical way to put these effects on "off", but keep some others.

I would be please to see some trails and explosions even if I have to renonce water hits and the like that are causing blue screen.

At best they would rework this file a little or make a special file available for the owners of cards that are at problem.

Another thing that would be extremly helpful is to elimanate the stutter caused when effects occur miles away. Doesn't seem right that my FPS drops to 10 because my panicky wingman is popping flares 2 miles behind me.

I just got this blue screen during a very long mission which I was recording

I have a Geforce Ti 4200 which is DX 8.1 compatible.

I get that blue screen when I use the F10 Map view - happens about 1 out of 10 occasions.

My system :
Athlon XP 2400+ (2.0GHz)
ASUS A7V266-e motherboard using VIA 4-in1 4.49 driver
1 GIG PC2100 ram
nVidia GF4 Ti4600 using 45.23 reference driver
Audigy 1 soundcard using latest EAX4 driver
DirectX 9.0b
Windows XP + SP1

I think we're narrowing it: yes maybe only the water effect is messing the entire effects file! My feeling is that really not much effects are at fault since before a blue screen occurs, I'm able to display a lot of nice trails and explosions.
Also some F keys are triggering the blue screen, external view or map view (these I don't have myself ).

Water effects cause an EXTREME hit on my machine, much more than any other effect in fact. If I miss my target and strafe the water, I might as well go make myself another cup of coffee while the FPS sort themselves out.

I think this kind of thing goes beyond 'tweak your machine before you play LOMAC' and hopefully the forthcoming patch will straighten thing out.

ASUS A7N8X Deluxe Rev. 2
AMD XP2800+
1 Gig Crucial PC2700
ASUS GeForce 5600 256MB DDR w/ Dets 52.16 (also tried 53.03, 45.23, 45.44?)
Windows XP Home SP1
Audigy 2
DirectX 9.0b

Hmmm, I posted re this same prob. You guys were onto it as I typed..But interesting, that those with relatively high end systems are having the same prob. Very interesting.......

I've got a GF2 MX400 and DirectX 8.1 installed. Deleting my former driver (which was 41.09) and installing the 30.82 driver, like suggestion somewhere on the ubi board, did the trick for me. I have effects set at "high" now and things can happily splash into the water and everything SO FAR . Anti Aliasing and that other thing is off, too, like suggested in the readme file (or was it on some of the boards? Man, all those tips and all that help is confusing me ).

Regards
heartc

Just having DirectX 8.1 or above installed on your computer is not good enough. Your video card must be able to utilize the effects and features of DirectX 8.1 to work properly.

Lock On uses effects and features based on DX 8.1. There is no way to make it backwards compatible to early versions of DirectX.

Carl

I use DX9.0b, have a GF4 ti4200 yada yada and i still get the blue ALOT...if u want to replicate...try alt/tabbin which i know isn't really good for any game but it produces the same result as lookin at the map too many times etc...

One thing i noticed...when u get this blue screen...even tho u can't see squat....hit ur zoom in/out and/or ur view hat...for me...certain zooms are blue and at various points, i can see stuff...tho parts of my cockpit may be missing etc. I've seen similar stuff happening in cames where textures are "colliding" or "clipping"

I don't think its driver related...as i get the same from 42.xx nvidia drivers all the way to the present 52.xx drivers
I'm no expert, but if u ask me..it has something to do with the game's (cards?) ability to re-draw the game after viewing something else...that wud explain the similar result when alt/tabbing out and then back, or looking at the map and then returning to the game

I did get BSOD when I first installed Lomac, particulary in external views while rotating the camera position around the a/c. However the error displayed was something like "an error has occurred in nv4disp.dll" - this made me think that the Nvidia drivers I was using weren't correct for Lomac. I have a Ti4600 and DX9b and didn't want to go to the 50 series drivers but did upgrade to the last of the 40s. I have not experienced a blue screen since then even after flying continuous sessions all Sunday (yesterday). Don't know if that helps anyone but perhaps it might. At least you might want to post up the general gist of the blue screen error you're getting and see if it gives anyone and/or the devs a clue to help you.

Cheers,
Stonehouse

Anyone here running the Nvidia fx5200 cards, how are they handling things...??

check ur lomac TEMP files for errors...this one, or one very similar seems common after each blue screen and/or lockup

Also...DXDIAG shows all running perfectly with no errors btw


12/7/2003 19:24
LandModelManager: can't find #model 15 LightPolygon
LandModelManager: can't find #model 15 CloudShadow
ModelManager: can't find LAP-CABLES
ModelManager: can't find GAZ-2410
ModelManager: can't find VAZ-2107
DXDefTexture: failed to load C-130-PAINT-DEF1.bmp, D3DXERR_INVALIDDATA.
StartShelterDoorOperation 139a OpenDXDefTexture: failed to load wpp-rul-1.bmp, D3DXERR_INVALIDDATA.
DXDefTexture: failed to load samara-red.bmp, D3DXERR_INVALIDDATA.
DXDefTexture: failed to load samara-blue.bmp, D3DXERR_INVALIDDATA.
DXDefTexture: failed to load samara-cherry.bmp, D3DXERR_INVALIDDATA.
DXDefTexture: failed to load night-city1.bmp, D3DXERR_INVALIDDATA.
Warning: (effect class Graphics::DXProjLight) must be loaded to step 1, step 0 reported.
Warning: (effect class Graphics::DXProjLight) must be loaded to step 2, step 1 reported.
StartShelterDoorOperation 1392 OpenStartShelterDoorOperation 139a CloseStartShelterDoorOperation 1392 CloseWarning: (texture class Graphics::DXFontTexture) must be loaded to step 2, step 1 reported.
StartShelterDoorOperation 139a OpenWarning: (effect class Graphics::DXProjLight) must be loaded to step 1, step 0 reported.
Warning: (effect class Graphics::DXProjLight) must be loaded to step 2, step 1 reported.
StartShelterDoorOperation 1392 OpenWarning: (texture class Graphics::DXFontTexture) must be loaded to step 2, step 1 reported.
StartShelterDoorOperation 139a CloseStartShelterDoorOperation 1392 CloseWarning: (texture class Graphics::DXFontTexture) must be loaded to step 2, step 1 reported.
StartShelterDoorOperation 139a OpenWarning: (effect class Graphics::DXProjLight) must be loaded to step 1, step 0 reported.
Warning: (effect class Graphics::DXProjLight) must be loaded to step 2, step 1 reported.
StartShelterDoorOperation 1392 OpenStartShelterDoorOperation 139a CloseStartShelterDoorOperation 1392 CloseWarning: (texture class Graphics::DXFontTexture) must be loaded to step 2, step 1 reported.
Warning: (texture class Graphics::DXFontTexture) must be loaded to step 2, step 1 reported.
Warning: (texture class Graphics::DXFontTexture) must be loaded to step 1, step 0 reported.
Warning: (texture class Graphics::DXFontTexture) must be loaded to step 1, step 0 reported.
Warning: ParticleNormalAlphaMap (texture class ParticleNormalAlphaMap) must be loaded to step 2, step 1 reported.
Warning: (texture class Graphics::DXFontTexture) must be loaded to step 2, step 1 reported.
Warning: ParticleNormalAlphaMap (texture class ParticleNormalAlphaMap) must be loaded to step 2, step 1 reported.
Warning: (texture class Graphics::DXFontTexture) must be loaded to step 2, step 1 reported.
DXDefTexture: failed to load f-16-okras-r.bmp, D3DXERR_INVALIDDATA.
Warning: f-16-okras-r.bmp (texture class Graphics::DXDefTexture) must be loaded to step 1, step 0 reported.
wWorld::Clean_World(): RegisterManager failed to clean up