FC3 Bug thread

[Alfa]

Today's list:

 

- MiG-29A fuel indicator TEXTURE is the same as the C version, this is incorrect. But the gauge still moves in the original, ergo you see a fake amount. This WAS CORRECT in FC2. But since ricardo pits . . . (there should be different fuel indicator in 29A / 29C)

 

Actually the "MiG-29A" fuel indicator was not correct in FC2.

 

In FC2 the MiG-29(9-12) was depicted with the ability to carry 1150L wing tanks - this is ok as the real life 9-12 often is backfitted with this feature, but the wingtank kit also includes a new fuelgauge like the one in the MiG-29S.

 

So the 9-12 should either have the original fuelgauge/no wingtank ability or 9-13 fuelgauge/wingtank ability.

[Azrayen]

- and EOS displays "AP" indicating active radar frequency jamming, well I don't think I have to comment this one. (but my guts telling me there is some sneaky conspiracy is behind this)

Uh, that's an old one IIRC. :)

[159th_Viper]

Uh, that's an old one IIRC. :)

 

Kindly enlighten me :)

 

I'm a Toadie so forgive the ignorance, but what exactly is wrong and what must be done to correct it?

[IvanK]

Mirror Landing System on Kuznetsov is hardly usable as the "ball' and its reference lights can hardly be seen at all. Ideally the ball and reference lights should be clearly visible by say 1.5Km from the stern. USN SOP is to call the ball by 3/4nm ... about 1.5Km

 

I haven't checked the US CV yet... EDIT USN CV is the same.

Edited November 21, 2012 by IvanK

[Kuky]

Also a question: Shouldn't the weapon quantity and maybe the interval selector work for rockets as for bombs? I might recal some pictures or videos that an Su-25 fired from 4 blocks at the same time. (couldn't find it though)

 

this actually works

[59th_Buncsi]

Actually the "MiG-29A" fuel indicator was not correct in FC2.

 

In FC2 the MiG-29(9-12) was depicted with the ability to carry 1150L wing tanks - this is ok as the real life 9-12 often is backfitted with this feature, but the wingtank kit also includes a new fuelgauge like the one in the MiG-29S.

 

So the 9-12 should either have the original fuelgauge/no wingtank ability or 9-13 fuelgauge/wingtank ability.

 

You may right about it, but the 9.12 is rarely equipped with this loadout and as i know only the russian and german (now polish) 29s were able to carry them. And the germans had the same fuel indicator as the hungarian and ours werent able to carry wingtanks.

[Alfa]

You may right about it, but the 9.12 is rarely equipped with this loadout and as i know only the russian and german (now polish) 29s were able to carry them.

 

Well I also prefer the old indicator for the 9-12 (I chose that for my MiG-29 3d cockpit project ) for that reason, so I am not advocating one constallation over the other Buncsi - just saying that it needs to be either one or the other :)

 

And the germans had the same fuel indicator as the hungarian and ours werent able to carry wingtanks.

 

The Luftwaffe fulcrums had the same fuel indicator initially yes - but then they went and purchased the wingtank kit from Russia and the fuel indicator changed :)

 

Before:

 

After:

[159th_Viper]

 

SU25A: No differences between takeof and taxi landing lights.

 

 

What difference should there be?

 

Screenshots please.

[Azrayen]

- and EOS displays "AP" indicating active radar frequency jamming, well I don't think I have to comment this one. (but my guts telling me there is some sneaky conspiracy is behind this)

Uh, that's an old one IIRC. :)

Kindly enlighten me :)

 

I'm a Toadie so forgive the ignorance, but what exactly is wrong and what must be done to correct it?

Whoops, sorry Viper.

Disclaimer: I didn't make the test in FC3, so let's go from memory.

 

In the HUD of the russian fighters, there is an indication ("Aл" center left) that an active radar frequency jamming is in progress (=someone jams you). This is a general indication. Then, contacts on the HUD are displayed in a different manner (vertical line/blinking) if they are jamming.

To summarize :

- "Aл" indication = jamming is detected

- individual contacts symbols = individual contacts are jamming or not

Now, the problem is that detecting a jam is done through the radar.

But, with the EOS on (and radar off), you got the "Aл" indication too.

-> bug, it's AFAIK not possible to know there is jamming ahead unless you use your radar to assess that.

-> "cheat" as you can use that to know there is an aircraft jamming in roughly that direction, without having to swith your radar on (hence staying discret, not picked up by other's RWRs).

[Ironhand]

...

But, with the EOS on (and radar off), you got the "Aл" indication too.

-> bug, it's AFAIK not possible to know there is jamming ahead unless you use your radar to assess that...

From what I've read, the MiG-29 can use the IR system while the radar is on but in standby mode. I'm wondering if, in such a configuration, the radar could still receive and know about the jamming without actively transmitting. If that were the case, then what you're seeing could be correct with the correct switch selection. In the sim, we don't have the same control over the two systems that Mig pilots apparently have.

 

 

Rich

[159th_Viper]

....the radar could still receive and know about the jamming without actively transmitting.

 

Makes perfect sense.

[159th_Viper]

List Updated:

 

1 - F15 Gear up = black textures

2 - Mig29S external fuel tanks not displayed on fuel tape # Feature and working as intended - *Under Revision* *Resolved*

3 - F15 ADI switched

4 - F15 Virtual head movement excessive

5 - Russian planes Cannot lock contact in TWS

6 - AK arrestor cables not animated # Fixed in latest revisions.

7 - SU33 loadout indicators reversed in cockpit

8 - Refuelling F15/SU33 buggy

9 - F15 VSD text overlap when STT/Guns

10 - F15 external lights absent in flight

11 - Damage modelling to wheels/landing gear absent

12 - F15 HUD unreadable

13 - Russian planes Nav circle misalignment in ENR/RTN modes

15 - R27ER no loft trajectory *No Bug - As Intended*

16 - Mig31 nosewheel not grounded

17 - Canopy jettison animation wrong

18 - EOS scanning not functional in elevation

19 - SU-27 cockpit textures include English labels. Not consistent translation. Examples: MSL and GUN on the weapons panel

20 - SU27 entire RWR is in English

21 - SU-27 native HUD "ИЗЛ" symbol overlaps over distance scale in BVR mode with Radar on

22 - F15 HUD indications overlapping

23 - Su-25, Su-25T and Mig-29 Caution, Warning and Trim lights are in english instead of russian letters

24 - HUD contacts in front appears also in Rear Aspect Mode.

25 - Frontal aspect HUD contacts appears in Rear radar mode and can be locked

26 - SU33 Green HUD block at night effect

27 - A10 ADI switched

28 - F15 black cockpit pixelation when facing northerly direction (afternoon)

29 - MIG29 Command Airspeed in LDG mode way below minimum

30 - SU27 Command Airspeed in LDG mode slightly below minimum

31 - Graphical glitch (hash marks) in lower centre of SU27 HUD when zoomed out

32 - Graphical glitch (hash marks) in lower centre of SU33 HUD when zoomed out

33 - F15 no drag increase with external fuel tanks

34 - Flyables smoke pod colours are incorrectly designated

35 - Scripting for cobra not present

36 - AIM-120C/R-77 tracks target beyond gimbal limits ONLY IF platform's radar reacquires target *No Bug - As Intended*

37 - Ballistic AIM-120C/R-77 locks target beyond FOV/Gimbal limits ONLY IF platform's radar reacquires target *No Bug - As Intended*

38 - SU27 automated leading edge flaps on flanker are shown in pit instruments as regular flaps

39 - SU27 when leading edge flaps are operational audio is heard for normal flaps

40 - FC2/FC3 mission incompatibility *Resolved*

41 - F-15C CTD initiated by changing the weapons (CTD when the player lock in the NAV mode a target with the radar and change the weapons)

42 - SU33 floating on pitching AK deck

43 - SU27/33 weapon panel characters misalignment if the cockpit illumination is on

44 - G940 HOTAS FFB issues/not functioning correctly

45 - F15 unable to adjust altimeter pressure setting at all. *No Fix required - Not a design feature*

46 - F-15C antenna does not track PTD in elevation with TWS

47 - Air to Air missiles do not have INS *No Fix required - Not a design feature*

48 - ECM uses FC2 behaviour in DCS world

49 - Missiles expend too much speed when turning

50 - Short range missiles do not turn hard enough

51 - Virtual Pilot G-Tolerance is too low

52 - Helicopters are exhibiting stealth characteristics

53 - SU25A Airbrake Pylons keep defaulting to the Russian SU-25 1st skin and the bort numbers become an outline in external view when zoomed out.

54 - SU33/27, Mig29 RWR does not indicate A.I. missile launch. Multiplayer bug only affecting clients and not host.

55 - Russian HUD guidance symbology in LNDG mode incorrect - missing glide slope error circle at certain runways

56 - Russian plane pilots have corrupted Pilot head textures at night

57 - Russian planes have corrupted landing light animations - MiG-29A,G/S and Su-27/33 have incorrect landing light animations

58 - Missile HOJ mode not functional

59 - Mig29 incorrect flaps deployed for player-controlled aircraft

60 - Multiplayer datalink not functional for Russian aircraft

61 - F15 no afterburner LED on right panel to indicate burner lit

62 - F15 flaps do not induce any drag

63 - F15 strange attitude/behaviour with crosswind landings

64 - AIM9 drops away before accelerating at launch

65 - Chimney smoke visible through undercast

66 - Mig29 flaps not extending to full 25 degrees

67 - Mig 29 flap extension animation incorrect

68 - Mig29 flaps blown in by wind at very low airspeeds

69 - Mig29 Chaff and Flare loaded amount incorrect when rearming in game, via the radio (Alt + ' ) menu

70 - Russian planes slip indicators and HSI offset from centre

71 - Multiplayer audio from other players not present (drogue chute)

72 - Multiplayer exhaust nozzle expansion not visible to other clients

73 - SU27 gets AoA warning of F15

74 - Water not visible in mirrors of FC3 aircraft

75 - Wingtip vapour effect missing from flyables

76 - SU25A antenna on nose cannot be seen from cockpit

77 - Contrails misaligned/too close to engines of aircraft

78 - Missile smoke discoloured/blue effect

79 - F15 does not repair

80 - Multiplayer clients do not see SU25A/T airbrake deployment

81 - F15 turbine fans not spinning

82 - F15 Gun pipper tracking issue (Impact point below target)

83 - SU27 Engines fully functional even when on fire

84 - SU33 Command IAS too low in LDG mode

85 - SU33 In-cockpit Weapons station indicator has 11 stations lit instead of 10

86 - SU33/27 and Mig29 Missile fire Zone computations bugged

87 - F15 Air intakes appears to be without any animation.

88 - Multiplayer Mig-29 repair on ground/at airbase not functioning correctly

89 - SU25A Wrong Chaff and flare count. 128 places instead of 256, model and skin shows 8*32 dispensers.

90 - SU 25A/T MDB-67-U 4*FAB-100 modell is incorrect, FAB-100 bombs too close to each other

91 - SU25A/T Gunpods operation cannot be asigned to axis

92 - Multiplayer disappearing player names from the menu in multi-monitor setups

93 - Missiles not aligned with weapons-pylon when SU-33 wings are folded

94 - R-77 not select-able whilst in Fi0 mode

95 - No TTI indicator on Mig29/SU27/SU33

96 - ILS Bugs/Inconsistencies in SU-27

97 - SU27/SU33 EOS not slewable in Elevation

98 - SU27/SU33/MIG29S lack EOS Narrow Mode Scan

99 - Russian Helmet Designator Circle stays on target after lock

100 - IRST sensor is Gimbal-Fixed in search mode

101 - No audio tone when HMS locks target

102 - HMS Targeting Ring behaviour/illustration incorrect

103 - Multiplayer: If client is killed by other player/unit he does not get losses in stats

104 - Mig29 Canopy Jettison lever transparent at night

105 - Russian Pilot kneeboard showing incorrect map of Crimea

106 - SU27 audio for flaps deployment not heard in external view

107 - SU27 Flaps retraction audio is played twice instead of once

108 - Wind does not affect chaff, flares and smoke markers

109 - No heat blur on jet engines when spooling up or at idle

110 - Mig29A can be rearmed with R27ER and R27ET in ingame rearming menu

111 - SU25A/T drogue chute cap remains open after first rearming

112 - SU25A/T takeoff flaps is shown as landing flaps on client aircraft

113 - F-15 Localizer Deviation Bar exhibits incorrect behaviour in banking maneuvers

114 - F15C mission wingman #4 in radio menu

115 - Floating Ghost Missiles in Multiplayer

116 - SU25A Inner Flaps defaults to the Russian SU-25 1st skin in external view

117 - Contrails visible through Clouds

118 - Landing reference lights on Admiral Kuznetsov very dim and unclear

119 - Mig29 External Fuel tank creates no drag

120 - SU25A Gear Lights Far setting not functioning correctly

 

 

 

Missed anything?

 

Shout.

FYI:

 

**As an aside, it is not all doom and gloom when one has regard to the list. At present and at this time of posting, approximately 50-odd issues have already been rectified with the rest having been assigned and receiving attention from the relevant developers**

Edited November 21, 2012 by 159th_Viper

[59th_LeFty]

What difference should there be?

 

Screenshots please.

 

Different angle. It is a three-stage switch, and two of it works the same.

 

Makes perfect sense.

 

In this case, give us a radar-eos joint ooperation switch, and a radar illumination master switch :) This would also eliminate the problem that if eos loses lock, radar automatically try to lock it (even is not switched on), so your cover is blown. Put this to the list if you want.

Edited November 21, 2012 by 59th_LeFty

[159th_Viper]

Different angle. It is a three-stage switch, and two of it works the same.

 

Referring to the gear lights, yes? If so, noted.

 

 

This would also eliminate the problem that if eos loses lock, radar automatically try to lock it (even is not switched on)

 

Is this a bug?

[Mechanist]

Quote:

Originally Posted by Mechanist View Post

Also a question: Shouldn't the weapon quantity and maybe the interval selector work for rockets as for bombs? I might recal some pictures or videos that an Su-25 fired from 4 blocks at the same time. (couldn't find it though)

this actually works

 

I've tested today armed only with rockets S-24-s and S-8 Blocks and non of the quantity / delay option worked?

 

Colud you make a track where it actually works as for the bombs? Thank you!

[Cali]

That's a lot of bugs, need more testers......:music_whistling:

[NRG-Vampire]

That's a lot of bugs, need more testers......:music_whistling:

 

Why ? You need more discovered bugs ? :D

I think we need more bug-solvers.

Here is another bug: thrust vectoring R-27 ? :doh:

Flame axis must be on longitudinal axis (except AIM-9X and R-73)

[59th_LeFty]

Referring to the gear lights, yes? If so, noted.

 

Su-25A, and her lamps are in the wingtips.

[Pilotasso]

Why ? You need more discovered bugs ? :D

I think we need more bug-solvers.

Here is another bug: thrust vectoring R-27 ? :doh:

Flame axis must be on longitudinal axis (except AIM-9X and R-73)

 

 

just a visual effect as the missile is flying with an angle of attack. Unfortunatly it is not very convincing as jet physics are not modeled.

Edited November 21, 2012 by Pilotasso

[Axion]

Su-33

 

Both engines on fire at Zugdidi, managed to fly 457 KM and land at Anapa, achieving angels 24 at mach 1.25 with both throttles at idle. Only slowed when fuel tanks were empty.

[Frostie]

Whoops, sorry Viper.

Disclaimer: I didn't make the test in FC3, so let's go from memory.

 

In the HUD of the russian fighters, there is an indication ("Aл" center left) that an active radar frequency jamming is in progress (=someone jams you). This is a general indication. Then, contacts on the HUD are displayed in a different manner (vertical line/blinking) if they are jamming.

To summarize :

- "Aл" indication = jamming is detected

- individual contacts symbols = individual contacts are jamming or not

Now, the problem is that detecting a jam is done through the radar.

But, with the EOS on (and radar off), you got the "Aл" indication too.

-> bug, it's AFAIK not possible to know there is jamming ahead unless you use your radar to assess that.

-> "cheat" as you can use that to know there is an aircraft jamming in roughly that direction, without having to swith your radar on (hence staying discret, not picked up by other's RWRs).

 

Hold on. While in radar mode in FC this symbol rightly means active jamming, but when in EOS mode it has nothing to do with jamming. What it signifies on EOS is the presence of a heat source (contact), it is letting you know that the EOS detects a contact.

[Axion]

Frostie, is this documented? Feel as though I'm missing a trick somewhere.

[Burro]

Acceleration Test Su-27/F-15

600 to 1,100 km/h, altitude 1000m, fuel 50%, no weapon

FC3 : Su-27 - 22sec / F-15 - 15sec

real world : Su-27 - 14-15sec / F-15 - 14sec

 

something with su-27 is bad

 

flight manuals Su-27, Mig-29, F-15 https://hotfile.com/dl/180329497/ef5...nuals.rar.html

Edited November 22, 2012 by Burro

[speckfire]

Acceleration Test Su-27/F-15

600 to 1,100 km/h, altitude 1000m, fuel 50%, no weapon

FC3 : Su-27 - 22sec / F-15 - 15sec

real world : Su-27 - 14-15sec / F-15 - 14sec

 

something with su-27 is bad

 

Interesting!!! Do you have a source for this?

[Burro]

I used a lot of resources, I have a flight manual Su-27, Mig-29, F-15 ,

just use google. Acceleration and climbing ability Su-27 is a major problem in the flight model FC3

Edited November 21, 2012 by Burro