FC3 Bug thread

[_Dredd]

Dredd I believe this problem has already been reported by 44th Rooster on the bugtracking database, expected it fixed in 1.2.5.

 

Missed that report, good to know. Thanks :thumbup:

[blkspade]

Dredd I believe this problem has already been reported by 44th Rooster on the bugtracking database, expected it fixed in 1.2.5.

 

I find it interesting and annoying that this is bug from FC2.

[71st_Mastiff]

I find it interesting and annoying that this is bug from FC2.

 

yes I get it too happens when I switch from bvr to ilsn. :thumbup:

[elemenohpee]

How to fix the mouse bug ? In my game not show the yellow cross for click on the panel buttons.

[KaspeR32]

How to fix the mouse bug ? In my game not show the yellow cross for click on the panel buttons.

 

That would be because you cannot click anything in the cockpits. This is Flaming Cliffs. No clickable cockpits included. Sorry :(

[Silver_Dragon]

any update bug resolver / unresolved list?

[Pelmo]

...

[L0op8ack]

Latest update,

F15C IFF is purely ranged based( magic range: 25nm/STT or TWS ), NTCR is broken.

 

Range: 25.2 nm, target unkown

 

Range: 24.9 nm, target identified

Edited July 4, 2013 by L0op8ack

[seikdel]

The MERs on the Su-25 seem to be borked. I load up my 32 FAB-100s, take off with visions of Arc Light dancing in my head, set my ripple quantity to all and my interval to the KMGU-MBR setting, pull the trigger and... I'm suddenly met with the disappointing sound of all my little gifts of joy dropping simultaneously. Hell of a cluster bomb, but not very effective for the aforementioned delusions of being a strategic bomber.

 

Anyone else?

[71st_Mastiff]

Latest update,

F15C IFF is purely ranged based( magic range: 25nm/STT or TWS ), NTCR is broken.

 

Range: 25.2 nm, target unkown

[ATTACH]84450[/ATTACH]

 

Range: 24.9 nm, target identified

[ATTACH]84451[/ATTACH]

Thats been reported, since 1.2.4

[Kuky]

The MERs on the Su-25 seem to be borked. I load up my 32 FAB-100s, take off with visions of Arc Light dancing in my head, set my ripple quantity to all and my interval to the KMGU-MBR setting, pull the trigger and... I'm suddenly met with the disappointing sound of all my little gifts of joy dropping simultaneously. Hell of a cluster bomb, but not very effective for the aforementioned delusions of being a strategic bomber.

 

Anyone else?

 

KMGU-MBR setting for delay works for this weapon only (KMGU bomblet canisters). Instead use 0.1, 0.2, 0.3, 0.4 time delay setting

[seikdel]

Oh! That's... new and different from the established tutorials. I thought the "MBR" was Cyrillic for "MER", i.e. multiple ejector rack. I guess giving us control over the actual interval is an improvement, though. Can't believe I didn't think to try this myself.

 

This is new functionality, right? I'm not just crazy?

[diveplane]

A10A cockpit minor find visual bug.

 

screen below

 

build 1.2.4 12913

[hypersonik]

does the (J) auto thrust for the F15 not working considered a glitch o bug ? worked on

1.2.3

[sslechta]

It was intentionally disabled by ED. See some of Wags previous posts for more info.

[blkspade]

Latest update,

F15C IFF is purely ranged based( magic range: 25nm/STT or TWS ), NTCR is broken.

 

Range: 25.2 nm, target unkown

[ATTACH]84450[/ATTACH]

 

Range: 24.9 nm, target identified

[ATTACH]84451[/ATTACH]

 

Are you referring to in game or IRL? In game at least IFF is limitless, the NCTR works at roughly 25nm so it doesn't really seem all that broken. What is broken about NCTR is the identification of the A-10C, as it remains unknown at all ranges. Also targets don't get ID'ed via NCTR within range when somewhere beyond 30 degrees off your nose.

[sslechta]

does the (J) auto thrust for the F15 not working considered a glitch o bug ? worked on

1.2.3

 

I found the thread I was looking for Hypersonik: http://forums.eagle.ru/showpost.php?p=1764526&postcount=6

 

Here's the line: Su-33. Auto-thrust will now only engage after route/return/landing autopilot mode is engaged. Auto-thrust for the other aircraft was not realistic and thus removed.

[uboats]

FC3 su-27 bugs:

Landing at Sochi from sea side, in LNDG mode, no glide error circle.

su-27 HUD has a white line in the middle after I reinstall the DCS world. It appears in common view angles. But in some special angles, it becomes hard to see.

Previously, I did not see such white line. I know it's due to two glass of HUD, but I want to know what cause this render problem.

[L0op8ack]

Are you referring to in game or IRL? In game at least IFF is limitless, the NCTR works at roughly 25nm so it doesn't really seem all that broken. What is broken about NCTR is the identification of the A-10C, as it remains unknown at all ranges. Also targets don't get ID'ed via NCTR within range when somewhere beyond 30 degrees off your nose.

 

OK, something interesting.

target ~50 degree right to my nose

bank left vs bank right, different story.

 

VS

Edited July 21, 2013 by L0op8ack

[Teknetinium]

From what I have been told (NOT my opinion) it is actually not a bug. According to the manual this is functioning as it should (note, I tried the tester version, so what I saw may be a little different from what you saw):

 

I go SNP

SNP determines priority target after a full scan and auto-bugs

I pull the gate off the target

The radar re-evaluates the priority target after a full scan and auto-bugs.

 

Note that I have been told that the manual switch for this mode is the exception in actual operation, not the default - thus, you have a radar operating in its default setting, correctly.

 

I did not test whether holding onto the gate-motion control would keep it off and prevent STT when the programmed range is reached.

 

Then it would be better to get back to how it was in FC2, so you can simulate both options rather than default one only. This is not correct and can not be accepted since in default option downgrades a Su-27s situation awareness by 30% compared to FC2. Why not chose the other option instead since as experienced FC Su-27 pilot i can confirm that not having auto-lock is much more efficient.

 

Is the F-15 in default mode as well? since it does not auto-lock in TWS in FC3.

Su-27 main bugs:

EOS horizontal slewing is broken.

TWS is broken as described.

Adjust Semi-Active missiles chaff resistance.

[karambiatos]

noticed something strange with the lights on the su-27 after 1.2.5 when i load r-73 the ECM light is still there just floating, and the pylon is missing.

[seikdel]

KMGU-MBR setting for delay works for this weapon only (KMGU bomblet canisters). Instead use 0.1, 0.2, 0.3, 0.4 time delay setting

 

Now it's broken again. No matter what I set the interval knob to, it just releases all of the selected FAB-100s at once. It makes for a hell of a cluster bomb, but it's not too useful if I'm trying to strike a convoy that's all nice and lined up. Is there a new feature I'm not aware of?

[Brisse]

No idea if this is known or not but I cannot skim through 128 pages to check so here it is:

I just did the F15 instant action mission and my wingman got really close on the six of a MiG. He should have switched to guns of course but he kept spamming AIM120's on that MiG and of course it was way to close so they all just flew right past the MiG.

 

He did not switch to guns until he run out of missiles. Stupid wingman :)

 

I have a TacView replay if that helps. Just send me a PM if anyone want to see.

 

Edit: I'm using 1.2.5 with the latest hotfixes (2013-08-04)

[Oesau]

A-10A air refueling door indicator light isn't coming on and it also appears that no fuel is being taken onboard despite the boom operator saying so (after a good connection).

 

Can someone else please confirm my observations.

[Kuky]

noticed something strange with the lights on the su-27 after 1.2.5 when i load r-73 the ECM light is still there just floating, and the pylon is missing.

 

no such issues here. I have tried in both testing and public release and whenever I change weapons to missiles, pylon only or ECM pod it loads properly so must be something on your end. Repair DCS world.