FC2 Bug Thread

[Dave317]

I landed a bit fast and wonky in an su25 as i tried to straightening up on the runway my wingtip hit the ground. As it hit it made a noise like it should but when i was level again the noise didn't go away and stayed making the noise as i taxied down the taxiway.

[Loophole]

Small graphical glitch I noticed in a mission I picked at random: The shadow on the moon, when it is visible in daytime, does not match the direction of the sun.

 

Unluckily, I am not sure what the time of day was, or even which mission I was in at the time, but the sun was overhead, and the moon was about 30 degrees up. The terminator on the moon was vertical, with the sunlit side to the left.

[Dr_Watson]

- pressing next Nav waypoint in A10 hangs up when you get to the last waypoint...bug or intended. Need to change to different mode, then back to Nav to get back to waypoint 1 for example.

- distance to waypoint does not update when you change to A2G mode

- on A10 bomb practise, I takeoff then get the audible noise when you pass the inner/outer marker (i think thats what it is) but this beeping continues throuout the missions until I passed over it again during landing.

- Laucnhing missles is completely silent, hard to tell when its launched.

- In F15, Mach reads 1.2 but sonic boom not active?

- Damage model of enemy units, 100 rounds of A10 30mm causes the truck to explode 10 seconds after the pass....not very realisitc at all!

- SU25T unflyable when TV optics on, frame rate drops 75%, blackshark shows no frame rate drop for an identical graphics set up??

 

Some may not be bugs, I'm just getting back into Lockon after a while away. Great job though. Nightmare setting up the keys for each aircraft individually!!

[4csNIp]

I got this error in editor, when I tried to use the predator RQ-1

 

 

 

We used last night 2x Predators.. Its problem with you,not with game. Predator is working very well.

[59th_LeFty]

Wow, so many problems already :) Maybe just the cause of intense use... well, here's my 'list':

 

-AI B-52 fired AGM-86s upon impact, caused crash for me. Offline, and only the Buffs were in the game, and some tunguskas to defend. I haven't seen them engaging before the crash.

 

-All of our squad have noticed that on the second skin of the new Su-25A has a minor shadow-bug - the dash-number in the shadowed side of the plane is becoming black.

 

All in all, an excellent job, ED! That's the one we waited for, but it worth!

[159th_Royalman]

In the Su33 when trying to fire S25 unguided rockets:

 

If you place the targeting piper above the horizon, the range scale in the HUD will start flashing.

[Kuky]

^^^

I think that is normal since piper should be at the ground to estimate distance, if above horizon it's in infinity

[159th_Royalman]

Yes, but it really looks unnatural. The range scale changes very rapidly from 5km to 10km and the entire left side of the HUD flashes as well! I remember in FC1 it was different.

[Stangpilot]

That sounds like Adaptive AA in catalyst control panel. Change to lower level.

 

That might have done it, I played with a bunch of things on my own before seeing this including that, but didnt do it systematically enough to report if that is what fixed it... sorry

[JimMack]

Wow, so many problems already :) Maybe just the cause of intense use... well, here's my 'list':

 

-AI B-52 fired AGM-86s upon impact, caused crash for me. Offline, and only the Buffs were in the game, and some tunguskas to defend. I haven't seen them engaging before the crash.

 

-All of our squad have noticed that on the second skin of the new Su-25A has a minor shadow-bug - the dash-number in the shadowed side of the plane is becoming black.

 

All in all, an excellent job, ED! That's the one we waited for, but it worth!

 

It would be very helpful if after a crash, that you attach the track file (in temp folder) in a post.

[Altair_w]

First of all, I want to thank all ED team for the amazing work they put on FC2.

 

I just want to report an apparently unimportant bug and probably easy to solve, that really ruin the full immersion sensation of the whole combat.

The bug is about the bullet/explosion sounds on the planes: inside the cockpit, the damages to the plane are completely silent. The results are that it is impossible to realize when our plane is taking damage from flak or small missiles. The only way to know when the plane is damaged are the warnings if the plane is damaged enough. But if a single bullet hit our plane, we can't realize that.

Same for the missiles: if the plane is heavily damaged from a missile explosion, the explosion is inaudible from inside the cockpit. It is possible to hear the explosion only from external views, in case of pilot kill.

Also, the airbrake, gear, flaps sounds are extremely low, or even inaudible.

 

I tried to disable the dolby surround from my sound card, played with sound options of FC2, putting the script sound.samplerate = 48000 on autoexec.cfg and even put on sound.cfg Mode3D = false; for all the related samples but nothing changed.

 

This is not a problem of my OS or windows configuration. All the members of our squadron, with different OSs have this problem.

I really hope this bug will be fixed because FC2, whith its high details and efforts put even in the smaller things, give a totally awesome flight and combat experience, and this little bug really put it down a bit.

 

Best Regards

=S= Altair

[galagamo]

Hi guys, so far I have flow several planes in quick start and getting an odd issue.

 

For F-15 and Su-27, cockpits load up and look normal. For A-10 and Mig-29C, the cockpits look transparent. I can basically see through the all the landscape. There is outlines of the cockpit, but its just not there. Some gauges and warning lights are visible as solid objects, but everything else is transparent.

 

Did a clean install using Windows 7 64, have ATI Radeon 5850 running Catalyst 10.2.

I also experienced this bug with both FC1.12 and FC2.0. Its a driver issue, turning down Anti aliasing solved the issue for me.

And I also use a HD 5850.

[Ven]

I just downloaded the game last night so haven't played much but in the F15 Quick start mission, I can see the flame of the plane I shot down through the clouds. As if the flame is above the cloud. Minor but annoying.

[eurofor]

MLRS?

 

[4csNIp]

I hate bug with ''friend chat''... its realy irritates me.

[Sanch0]

A couple of graphics problems.

 

Before alt-tab:

 

After alt-tab

 

 

On the left side we can see Su-25T with nav lights on. On the right side are two fighters with nav lights on but we can't see it from distance...

[3Sqn_TomAce]

3Sqn like FC2.0 and give a big thumbs up so thanks again, two main things that we have picked up are:

 

* Tally issues WVR seems far to hard to see jets 1.5 mile +

* Notch seems far to effective on A/C radar we've seen contacts disappear from 60deg aspect

[Beniti]

Hi,

 

I've a little bug in multiplayer session. When I start in a hangar, its doors remain closed. It's weird because some of my teammates don't have this problem.

 

An idea ?

 

Thanks for your replies ;)

[slug88]

First of all, I want to thank all ED team for the amazing work they put on FC2.

 

I just want to report an apparently unimportant bug and probably easy to solve, that really ruin the full immersion sensation of the whole combat.

The bug is about the bullet/explosion sounds on the planes: inside the cockpit, the damages to the plane are completely silent. The results are that it is impossible to realize when our plane is taking damage from flak or small missiles. The only way to know when the plane is damaged are the warnings if the plane is damaged enough. But if a single bullet hit our plane, we can't realize that.

Same for the missiles: if the plane is heavily damaged from a missile explosion, the explosion is inaudible from inside the cockpit. It is possible to hear the explosion only from external views, in case of pilot kill.

Also, the airbrake, gear, flaps sounds are extremely low, or even inaudible.

 

I tried to disable the dolby surround from my sound card, played with sound options of FC2, putting the script sound.samplerate = 48000 on autoexec.cfg and even put on sound.cfg Mode3D = false; for all the related samples but nothing changed.

 

This is not a problem of my OS or windows configuration. All the members of our squadron, with different OSs have this problem.

I really hope this bug will be fixed because FC2, whith its high details and efforts put even in the smaller things, give a totally awesome flight and combat experience, and this little bug really put it down a bit.

 

Best Regards

=S= Altair

 

This isn't a bug. It's intentional. There are many accounts, both modern and from previous eras, of pilots returning home from sorties to find their aircraft with bullets holes and other damage, without ever having heard or felt the incoming fire. The cockpits of these aircraft are pretty well insulated, and the pilots' ears are further insulated by the helmet and earphones.

[Adder667th]

Possible bug with audio upon very hard landing

 

Hi, I dont think this one has been reported yet, sorry if it has.

 

This "bug" occourred in the SU-25T Ramp start and Nav mission.

 

After hard landing with main gear collapsed, nose wheel tyre popped and large fire at rear of A/C,

the LOUD CLUNKING noise that you can hear while in F2 external view does not stop, even after aircraft has come to complete stop and both engines have spooled down to zero rpm. Even after i eject it still goes on.

Possibly the sound is audio for the damage, it does sound like debris in the turbine or metal on tarmac from the damaged landing gear, which is pretty cool but it needs to stop :)

[Mugenjin]

Am I the only one who gets the Su-27 as a Mig-29 on the US RWR?

i.e. I played F-15 DACT BVR against Su-27, but on the RWR it showed 29 instead of 27. ?_?

[Shaman]

Because both use same radar unit, where one has larger antenna though.

[Napa]

Fantastic sim. LockOn the way it should be from the very start.;)

 

BUT!!!... Its time for some bug reports to help in improving this great sim :book:

 

1) The game is crashing after a while. To be honest, sometimes it crashes, sometimes it doesn't. How do I find or create a report for this??? (My specs are in my sig). I have cpuz to monitor cpu, hd, gpu, fan rpm and voltages and everything looks more than efficient. While I run FC2.0, 55c in the gpu (I disabled the multi-gpu on the GTX295 since Lockon runs better on 1 gpu and I get 5-10 fps increase) and 45-50c on the cpu depending on room temp. It could be driver problems although I have installed the latest nvidia drivers 197.13.

 

2) In the A-10 campaign the missions are repeated twice although I'm getting a 100% completion and I get the message that the mission has been completed.. when I exit and select the campaign again the next mission is the same as the last one. When I finish the mission twice I get to move into the next one...:noexpression: This never happened with BlackShark AND the F-15C campaign.:huh:

[connos]

2) In the A-10 campaign the missions are repeated twice although I'm getting a 100% completion and I get the message that the mission has been completed.. when I exit and select the campaign again the next mission is the same as the last one. When I finish the mission twice I get to move into the next one...:noexpression: This never happened with BlackShark AND the F-15C campaign.:huh:

 

I have the same issue with the A10 Campaign.

[Distiler]

There is a minor mistake in the name of a mission "MP Total Air War 56õ56" (notice the õ, I think it should be vs). No problems in my Windows, but a chinesse Windows might have problems with it. Check this:

 

http://forums.eagle.ru/showpost.php?p=860641&postcount=10