FC3 Bug thread

[IvanK]

Thanks Kuky. What is the Diamond doing ? Does it remain on the designated point ?

[IvanK]

Here is a TRK that illustrates the CCRP issue as described by Fouga. The target is the IL76 parked on the Eastern apron.

 

You can clearly see the diamond dropping short after the IL76 Target is designated by pressing and holding the pickle button. Using the Mission Editor Measure tool shows the 2nd bomb impact to be 275M short.... exactly where the diamond ends up

(Airspeeds are kept low in the track to ensure CCRP is forced without any possible reversion to CCIP)

 

 

CCIP works spot on.

 

CCIP/CCRP SELECTION (WISH)

More a whish than a bug. The current Russian system is to me quirky without there being a specfic CCIP/CCRP mode selection (like in A10). The Russian system in FC3 always defaults to CCIP UNLESS the current impact point lies outside the HUD field of View it then operates in CCRP. So from a piloting point of view you are in this grey area as to what you are going to get CCIP or CCRP. It would be nice for the pilot to decide the delivery mode. If carrying High Drag weapons then depending on Dive angle release altitude he may want CCRP. He might also want CCRP for Low drag weapons for a Dive Toss manoeuvre. At present in this scenario you will get CCIP since the impact point lies in the HUD FOV. If the pilot wants CCIP then its up to him to get the required Dive angle, Release TAS and altitude to have the impact point in the HUD FOV.

 

Wish: Manual selection of CCRP or CCIP via keybinding A la A10A.

SU27CCRPBUG.zip

[IvanK]

A10A ILS ????

 

This to me is totally bugged !

 

The old HUD Cross bars are bugged. I can only ever get the Horizontal (Glideslope) Bar displayed. The localiser slope scale never appears. In the A10A Manuals I have looked up there is no reference to any ILS info in the HUD anyway. I believe the vestige HUD Horizontal ILS bar should be removed completely. The only ILS references should be the HSI CDI bar and the ADI bars and Glideslope needle.

 

With respect the ADI Director bars the Glide slope bar seems to function okay however the Localiser bar is totally unusable as it responds directly to bank input and NOT localiser deviation. (This is a similar bug to all the FC3 aircraft in that HUD and or localiser directors all instantly respond to bank inputs... Unresolved bug no 113). The A10A however is the worst and renders the ADI localiser FD bar unusable. You can be on the localiser and using small bank inputs bounce the ADI Localiser bar off each side of the ADI with little actual localiser deviation.

 

The Localiser and Glide slope bars on the ADI should only respond/represent deviation from the respective Localiser and Glideslope.

The A10 does not I believe have a Flight Director function. As such the ADI bars are straight out deviation indicators and are therefore independent of Heading,Bank and intercept angle.

 

The HSI CDI bar should reflect the the deviation from the localiser and in effect reflect the same information as the ADI localiser deviation bars.

 

In ILS mode you seem to get a small designated point square (TD) in the HUD located in the centre of the runway... not sure of its purpose though ?

If you track the small square with Velocity vector once on final it does result in a good flight path approximating the Localiser and Glidesope until you get in close where it would take you above the Glideslope as the square is located at the centre point of the runway and not at the Glideslope intercept (GPI).

 

In this graphic we are on the Glideslope but well left of the Localiser. the HSI CDI is correct, the ADI Localiser bar says all is good and we are on the localiser !. Glideslope indicators on the ADI are both good.

 

 

Attached trk shows ILS in the A10A. As can be seen small bank inputs result in wild deviations of the ADI Localiser bar. Tracking the ADI bars is not really possible as any small correction to track or correct a slight deviation from the Localiser results in an immediate and opposite response from the ADI localiser bar.

A10AILS.zip

Edited June 1, 2013 by IvanK

[Mechanist]

Is this a Bug ? I'm not sure.

Having some Gunzo dogfight with the Su-25, I was able to use the Aiming pipper from CAC mode [6] and the Fixed reticle sight [8] at the same time ?!

 

I thought the [8] reticle was just a backup mode that replaces any other HUD indication.

 

EDIT : True for any combat mode, Ground [7] or CAC [6], with the Su-25 only ; no way to have both on Su-25T or any other Russian fighter.

 

It is more like an overlay than a real mode. MiG-21 will have the same, also here is a picture for reference, It is not entirely visible but you can see the grid edges

 

 

Also I use this grid mode for night flights and navigation to help me see the centerline of the aircraft.

[IvanK]

Another image showing both primary and backup reticles visible:

 

 

 

 

Edited June 1, 2013 by IvanK

[71st_Mastiff]

FC3 KC tanker.

 

KC tanker landed and then turned into this. lol What the?

[IvanK]

The 2 louvred intake grilles in the skin near the nose = FA18

[Kuky]

Thanks Kuky. What is the Diamond doing ? Does it remain on the designated point ?

 

Just tried CCRP in Su-27 again... it definitely looks working correct now in test build, the target area I designate with CCRP piper is where the targeting diamond is and where the bombs drop (more or less, I think bombs are not extremely accurate especially when there is some wind in mission).

 

PS: would I be right tossume the piper position should be little higher up in the HUD? For me to see where it's looking over terrain, I have to lean forward in the cockpit so that EOS sensor on the nose is not blocking it

 

PPS: I just tried latest public build and I could replicate the CCRP not being correct, the tageting diamond falls way too short of designated point and bombs also fall short and in area where targeting diamond was at. So, I would say this is definitely fixed in latest test builds and should be available into public version in future updates (but I don't know which one)

Edited June 1, 2013 by Kuky

[IvanK]

Thats good news Kuky, thanks.

 

Not sure on the Pipper position predesignate. In the MIG29 is sits right down the bottom as well, but there of course there is no issue with the EOS sensor.

Logically it would be better for the CCRP Pre designate pipper to sit at around 10 degrees or so.

 

In the F18 in AUTO/CCRP undesginated the CCRP pipper sits at -7.5 degrees so its easily visible, once Flight path angle reaches -7.5 degrees it sits on the velocity vector ... a much more sensible operation to that in the Russian birds :) .... makes it very easy to fly it on to a point to designate etc.

Edited June 1, 2013 by IvanK

[Pelmo]

PPS: I just tried latest public build and..

 

Kuky, can you tell us if they have improved the air to air missiles? Is there any news?

[Kuky]

ED is working on them Dio

 

To me IR missiles are much better then before... well they track better... the R-73 got some TVC but I think it needs more adjusting, for example of-bore angle for R-73 is still too low (missile should be able to track 90° of-bore I believe but this is not like this in game yet), The R-27 family is still the worst when it comes to tracking, so missiles still need more fixing.

 

Don't consider this as official news cause its not :) Also I am by no means missiles expert and I still just a tester so take my opinions as just opinions.

[Pelmo]

Ok, thank you!:thumbup:

[IvanK]

SU33 & CV OPS

 

Issues with SU33 and CV ops.

AOA INDEXER

The current SU33 mechanisation of the AOA indexer is IMO bugged and not logical.

The AOA indexer only operates when established on a Kuznetsov ILS. If not following

the CV ILS it does not work. It does not work when flying an ILS to a shore station either.

This makes no sense. All the indexer should do is provide an On speed AOA/IAS relationship when in the approach configuration.

 

USN mechanisation simply looks at Gear,Flap and Hook position. If the aircraft is in the Approach configuration the AOA indexer comes alive. If the Hook is not down the indexer will flash as a warning.

This flashing can be turned off using the Field/Carrier bypass switch ... like when landing on a runway with the hook up.

So the AOA indexer is usable on EVERY landing be it on a CV or a runway and doesn't require any Navigation aids associated with it. SU33 mechanisation should follow this logic to make it usable.

SU33 ON SPEED AOA

This seems to vary randomly. Following repetitive approaches at the same weight I get different IAS values for On Speed indications on a random basis. By experimentation it would seem 9 Deg AOA is in fact "ON SPEED" This ties in with an Approach IAS of around 270Kmh (Weight dependent of course). This also corresponds with the RED marker on the ASI circumference and what the Auto throttle drives to.

 

The Command IAS on the HUD is also changing throughout the approach. It typically starts at around 300KMH then reduces to a value around 270KMH at 300m RADALT. The convention for CV operations is to be "ON SPEED" throughout final approach. To this end it would make sense for the HUD Command IAS to be fixed at the approach value from the LDG activation waypoint at the latest. An easier method would be If in approach config Commad IAS should be ON Speed value. This would (if implimented as suggested) be consistent with AOA indexer operation. It would also be consistent with the AUTO throttle operation which seems to drive to 270KMH IAS

MIRROR LANDING SYSTEM

This is just not bright enough to be usable. It should be clearly visible on Approach from say 1Km out.

HUD "K" INDICATION

This is overwriting the LDG legend in the HUD

 

CV DECK LIGHTS

These are Time of Day dependant. They should also be Visibility dependent. So in Daylight Lo visibility conditions they should also be on. I would suggest if Visibility is < 1200m then Deck lights should be on. (Same should be implemented for runway lights http://forums.eagle.ru/showpost.php?p=1780926&postcount=1 )

Edited June 6, 2013 by IvanK

[Hardcard]

IRST/Over the Hump

 

Hi everyone.

 

I know this is listed under pending fixes, but it's really annoying me.

Does anyone know when ED is going to fix the IRST bug?

The IRST vertical axis is stuck, can't be oriented...this is rendering IRST useless when flying Russian fighters. I love R-27ET's but can't use them unless this bug is fixed... (I used to depend on them back in FC2)

 

Also, the MiG-29 campaing "Over the hump" seems broken:

1-Can't order Su-25's to start their SEAD because there is no F10 command.

2-Wingman is running at full afterburner ALL THE TIME, even when flying in formation at cruise speed (I know it doesn't make sense, but it's really happening to me). He ends up reaching bingo fuel before the action even starts.

 

 

Thanks!

[combatace]

I can still hear the AOA tone of F-15 in Su-27. Can something be done about it?

[Buzpilot]

Looks like #86 on Resolved list is not completed, the R-27ET don't have LA until it's really close. And the F-16 on Track ,AI on High, shoots AIM-120B too early, or the 120B has too small range.

F-16 AI High early shooter and R27ET short LA inside range.trk

[IvanK]

F15C Air to Air Refuelling READY light

 

In FC3 the "READY" light on the canopy bow illuminates once the Air refuelling door is opened. This is correct however once the Boom is engaged the ready light should extinguish and remain out as long as the boom is engaged. On disconnect the Ready light should again illuminate until the door is closed.

[IvanK]

DCS/FC3 F15 ADI STEERING BARS & OFF FLAGS

 

The ADI Steering bars and Course warning flags in the F15 are bugged. At present these bars are always visible on the ADI regardless of Steering modes. The ADI bars should only be visible when providing meaningful information. As in ILS or Course steering information. At other times the Steering bars should be "Parked".

 

PARKED POSITION

The horizontal or pitch bar when not in use is completely removed from the ADI and cannot be seen at all. (In the F15 in FC3 it sits at the bottom of the display) The vertical or bank steering bar when parked is placed to the extreme right of the ADI. The cropped image below is of an F15 ADI in flight (In an A/A mode as can be seen in the full un-cropped image). As can be seen the horizontal bar is not visible and the vertical bar is in the extreme right hand "parked" position. Also note no Red course warning flags are visible either.

 

 

These bars can also work independently. When Course line steering is active (the single vertical line in the HUD) then the vertical needle is active to provide a left Right reference to the pilot. The horizontal bar remains hidden.

 

When the ILS is selected both bars are visible and provide steering cues in both Azimuth and pitch to the pilot.

 

So if the HUD Integrated Flight Director cross is present then both ADI steering bars are visible.

If the HUD single line steering cue is displayed then similarly only the ADI vertical needle is active and moves from its parked position.

 

In Air to Air modes both needles should be parked.

 

This more or less agrees with the F15A-C Flight manuals though the description in there is not very detailed.

 

COURSE WARNING FLAGS

At present these are continuously displayed even when ILS is not selected (Select ILS mode then back to AA mode and the course warning flags come up) and the steering bars should be in the parked position. This is incorrect when the ADI bars are parked thecourse warning lags cannot be displayed.

 

Here is another example of COURSE WARNING flag bug. Established on the ILS with both course warning flags visible !

 

From a DCS point of view these red course warning flags should never be visible unless in say the ILS mode and then only if there is an issue with the received ILS signal or steering mode. Frankly I think in DCS/FC3 F15 they should be removed all together they are meaningless and confusing at present. Perhaps the only time we should see these is on Start up before power is supplied to the system. Similarly with power OFF both ADI steering bars should be visible centred on the ADI display. Once power is applied the ADI steering bars should move to their parked position and the course warning flags should disappear.

Edited June 9, 2013 by IvanK

[Mechanist]

Su-25A new cockpit miss the low altitude light. On the model/texture it is present but not working.

 

Also the green arrow turned to 100m on previous was 40m

 

Screnshots brightness turned a bit up to see the black box that should be red.

[Pelmo]

Please! Someone could update the list of Bug solved and not solved?

Maybe after the release of the next small patch for version 1.2.4?

Thank you!:thumbup:

Edited June 12, 2013 by Pelmo

[combatace]

I crash landed and broke my landing gear yet the landing lights of my su-27 light up the runway..

[RIPTIDE]

Haven't checked here in a while, but it appears that Ghost Datalink Contacts still exist in MP play at least, after Enemy Aircraft unit is destroyed. Not sure if a track is needed...

[blkspade]

I have noticed some anomalies and bugs in the F-15 campaign. Its become hard to tell which mission I'm on at this point number wise but its some where between 6-9 the Defensive CAP mission. The mission prior was seemingly unbeatable, until the 2nd to last update, but I was award a mission complete at the start of the mission after the update. On the current mission (which I've flown atleast 4 times) the AWACS escort fails to protect the AWACS every time from the SU-30s. According the radio chatter it seems like they are engaging, they just suck at their job, maybe they engage much too late. All my efforts to pass this mission have failed thus far, even though the only losses on our side to ever occur are our AWACS and occasionally one of my wingmen. Either my flight destroys the Su-25s or another (F-16s?). My flight pretty much always handles the SU-30s, and only once do I think the Mig29s even bothered entering our airspace or we theirs.

 

Another topic are the AI wingmen, and their abuse of JP8 and their unwillingness to AAR. One of them goes screaming bingo, I'll say hit the tanker. He'll respond copy, then immediately say rejoin. I figured out that when this happens you pretty much have to guide your flight to the tanker just to have one top off. Another instance #3 was stuck in line (chicks in tow) for a while, I hadn't realized and eventually sent #2 to refuel and he somehow went ahead of #3. Now in that case #2 was lined up and ready to refuel following the tanker closely enough to connect but never did, #3 went on to eject. With all immediate threats splashed I had to send #2 home.

[_Dredd]

I've had this freezing bug in the F-15C four times now but haven't been able to test further to find where/why it is exactly happening.

It seems to be the same that was reported here some time ago when I searched through the forums

http://forums.eagle.ru/showthread.php?p=1070577&highlight=Ils+mode+freeze#post1070577

 

I'll test more this week/weekend to try pinpoint when it's occurring. So far on a test dogfight mission I have when cycling through ILS points then cycle to nav,tacan, ILS near Batumi the game freezes but sounds continue. On one occasion the freeze stopped and game resumed after approx 15 secs, but other times it has just stayed frozen, and I have to Ctrl alt del to end the process. When I do from memory it appears there was a second dcs window open that I see occur when the game loads but screen height.width resolution conflict exists.

 

I am using a hotas hatswitch on the stick with a modifier button on hotas throttle as waypoint cycle function. I'll test with keyboard commands next time.

 

Edit: possibly related to this? I do have incomplete routes set for AI, only one fly to waypoint.

http://forums.eagle.ru/showpost.php?p=938829&postcount=13

Edited June 17, 2013 by _Dredd

[Mustang]

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