FC3 Bug thread

[Azrayen]

From what I've read, the MiG-29 can use the IR system while the radar is on but in standby mode.

That makes pefect sense. Off/StandBy/On are common modes in aeronautics systems.

- Off is "really off", not powered + will need some time to initialize/ do BITs...

- StandBy is "not in use", but also "ready to be used"

- On is "in use"/"active".

 

In that sense, it is perfectly OK to use EOS (On) with Radar in StandBy. That's only logical for the latter not to be Off. But it still is no conclusive proof of the bug (nor its absence). ;)

 

 

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.

Perhaps it's the case. I have no clue, but I have doubts because:

- in that case saying the (whole) radar is in StandBy would be wrong. We should describe the key as radar emitting yes/no, not as radar on/off, which we (nor ED) do not.

- if that's true, then why is "only" the general indication of jamming shown? Why not the contacts jamming on the HUD too?

Now, your hypothesis is interesting. There are knowleadgeable people here on MiG-29s/Su-27s. Could those people please give us their view on that topic? :)

(will ask elsewhere too)

 

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.

Is this a bug?

No. Feature request (an interesting one, but still).

 

 

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.

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

+1 with Axion's question. Interesting, Frostie, but if you have doc/link/reference on that, feel free to share. :)

Meanwhile, I will plan to test with buddies (to be sure if they are jamming or not) but can't be sure to do that quickly.

 

++

Az'

Edited November 21, 2012 by Azrayen

[159th_Viper]

I used a lot of resources...

 

Well then give me one, or more as the case may be.

 

I do not have time to google around and attempt to find information to validate your findings - there is too much else to attend to. It is up to you to substantiate your allegation. Once I have the required documents/proof that back up your findings only then can/will I report the matter accordingly.

[159th_Viper]

No. Feature request (an interesting one, but still).

 

I am referring to the Radar automatically switching on whilst in EOS mode.

[Frostie]

 

+1 with Axion's question. Interesting, Frostie, but if you have doc/link/reference on that, feel free to share. :)

Meanwhile, I will plan to test with buddies (to be sure if they are jamming or not) but can't be sure to do that quickly.

 

++

Az'

Just pointing out how it works in game no reference to what should be happening. I've since learned that these contacts are actually jamming so where we go from here no idea.

[Frostie]

I am referring to the Radar automatically switching on whilst in EOS mode.

Should your radar automatically switch on when you've turned it off? Why would you turn your radar off, it needs clarifying by someone whether what currently happens is a feature otherwise this is surely a bug.

[HungaroJET]

List Updated:

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

 

^ Fixed...download will be available soon (tomorrow) ;)

http://forum.lockon.ru/showthread.php?p=1611814#post1611814

 

%5Bimg%5Dhttp%3A//i.imgur.com/d7NIx.jpg[/img]

[159th_Viper]

^ Fixed...download will be available soon (tomorrow) ;)

 

Report refers to the operation of the Luna-3 OLS :)

[159th_Viper]

....otherwise this is surely a bug.

 

If the general consensus is that it is more probable than not a bug (IMHO yes because toggling radar on negates the stealth of EOS) then I will report it as such.

 

All I need is a track. Anybody care to put together a short one please?

 

Ta

[Burro]

Well then give me one, or more as the case may be.

 

I do not have time to google around and attempt to find information to validate your findings - there is too much else to attend to. It is up to you to substantiate your allegation. Once I have the required documents/proof that back up your findings only then can/will I report the matter accordingly.

 

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

[Azrayen]

If the general consensus is that it is more probable than not a bug (IMHO yes because toggling radar on negates the stealth of EOS) then I will report it as such.

Viper, I don't think it's a bug.

I think it's an useful (and probably realistic) feature, already implemented (and IIRC it's been there since LO 1.0 or 1.1 at least).

 

What is not implemented (= what I said was feature request) is the ability for the player to force the radar (emitter) Off. I.e. to ensure his level of stealth.

 

Now, we haven't that ability for now. How do we stay stealth? Simple: Learn how/why the EOS will loose the target, and thus the system will switch the radar emitter on to keep tracking that target. If you don't want radar, then unlock the target => the radar will stay off (you loose the lock, that's OK because the EOS was no more capable of keeping it).

 

I prefer to retain the already implemented auto-switch radar/EOS, which is very useful in a lot of engagements. I feel learning to use the target aspect and/or position relative to my plane is enough to ensure no auto-switch if I don't want it.

 

Frostie, I agree that it's not really off. See it as a standby mode, with authorization to go live ;)

I agree too that a "real" off mode (or, more exactly, a standby mode, without authorization to go live) would be nice, but that's a feature request, not a bug. :)

 

++

Az'

[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

 

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

 

Flight manuals Su-27, F-15, Mig-29 for you https://hotfile.com/dl/180329497/ef55fef/Flight_manuals.rar.html

[Teknetinium]

Is it mentioned that Su-27 can be seen from much grater distance then F15 in visual. Witch I dont think is correct, if F-15 dose not use any new technology that we don't know of :)

[159th_Viper]

Is it mentioned that Su-27 can be seen from much grater distance then F15 in visual.

 

Not yet.

 

Have you got screenshots?

[159th_Viper]

Flight manuals Su-27, F-15, Mig-29 for you https://hotfile.com/dl/180329497/ef55fef/Flight_manuals.rar.html

 

Ta

 

Can you let me know which page/paragraph of the SU27 manual I need to look at to see where the acceleration data is mentioned?

[Teknetinium]

Not yet.

 

Have you got screenshots?

 

 

Ill get you some.

[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

 

 

 

Flight manuals Su-27, F-15, Mig-29 for you https://hotfile.com/dl/180329497/ef55fef/Flight_manuals.rar.html

 

Wow what a wealth of information. Thanks a lot :D

Now I need to practice my Russian ;)

[Teknetinium]

In picture one, I have F-15 Locked.

And then there is another bug as you can see at closer range, picture two, Su-27 and Mig-29 become drones while there is still no visual on F-15:)

If it was not known, the bug need some attention.

Edited November 22, 2012 by Teknetinium

[GhostDog]

Posted this one about HOTAS button inputs not working in another thread, no reply there as of yet: http://forums.eagle.ru/showpost.php?p=1608533&postcount=4

[IvanK]

There has been some discussion on EOS scan volume limits in this Bug thread.

 

I went and did a test in the SU33. I am presuming in FC3 that all EOS systems on MIG29/SU27 and SU33 are the same. The aim was to establish the EOS angular dimensions.

 

In pitch it was relatively straight forward to determine that it is +15degreees to -15 degrees. this can be measured by direct digital readout of the Pitch on the HUD. I accept there may be a little bit of variance due to AOA.

 

Azimuth is a little harder. The image below has the Real aircraft target right on the EOS Azimuth limit.

 

 

 

 

I dont have any Cockpit Angular dimensions for the SU33/MIG29 but do for the FA18. Assuming the Pilots design eye and canopy bow are broadly similar in both types then The EOS azimuth limit would be 30Degrees Left and Right.

 

 

So to me its +-30degrees in Azimuth, +-15fegrees in elevation.

Edited November 22, 2012 by IvanK

[MarkuzJuniuz]

Is it mentioned that Su-27 can be seen from much grater distance then F15 in visual. Witch I dont think is correct, if F-15 dose not use any new technology that we don't know of :)

 

At first I was happy with this because it seems that I can see Su-27s far away as dots. Then I noticed it's the only aircraft I can easily spot as a dot from far away. In the instant action for F-15 the Su-27 even beats the bombers it's escorting (I think Tu-22) visibility wise.

 

Other aircraft aren't as easy to spot compared to the Su-27. I hope this is a feature that will work for all other aircraft. :P

[159th_Viper]

If it was not known, the bug need some attention.

 

Ta.

 

Yes, I see now - that is pretty bad.

 

Away to report.

[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

121 - SU-27 visible as large black dot from extreme visual distance

122 - SU-33, SU-27 and Mig-29 Gear Lights Halo not visible at night

 

 

Missed anything?

 

Shout.

Edited November 22, 2012 by 159th_Viper

[diveplane]

List Updated:

 

 

 

Missed anything?

 

Shout.[/quote

.....................................

 

graphic glitch su33/27 mig 29 omni landing lights not visible at night.

Edited November 22, 2012 by diveplane

[159th_Viper]

 

graphic glitch su33/27 mig 29 landing lights halo not visible at night.

 

Screenshots please.

[Cali]

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)

 

No, but maybe some of them could/would have been fixed before....if they were caught before. Ever heard 4 eyes are better than 2?

 

EDIT: Thanks Viper for keeping a running tally on these bugs.

Edited November 22, 2012 by Cali