FC3 Bug thread

[159th_Viper]

(You dont need further info on this one do you ?)

 

Just info on the range values.

[Kuky]

Viper a little advice ...

 

Put in Signature the link of last updated bug list and in addition to this the words ... "To report a bug, and in addition to the description is required trk ... Thanks"

 

I hope it will facilitate the work of the moderator!

 

Ciao

 

it's quite lot of work to keep everything up to date so frequently, I think Viper is actually doing a very good job keeping track of the list. Little checking on previous 2-3 pages doesn't hurt does it? :smilewink:

[59th_LeFty]

My experience On line in FC3 is that the AIM120C consistently out ranges the R27ER in head to head engagements. Is this in line with the Devs intentions ? I have always thought that the R27ER was the missile with the longer legs ?

 

The Ingame Encyclopaedia quotes ( I know these are not Dynamic values) range of 70Km/Mach 3 for the R27ER and 55Km/Mach 4 for both Aim120B/C.

 

In game Fire Zone comparisons (Using TWS values for Mig29 as STT values are bugged) provide the following values:

 

Situation Head on Co Speed 0.9M/7000m

 

R77

Rmax1 42Km Rmax2 15Km

 

R27ER

Rmax1 48Km Rmax2 20Km

 

AIM120C

Rmax1 55km (30nm) Rmax2 18Km (10nm)

 

One thing I'd comment on this - I've tested, and the AIM120C and R27ER hase EXACTLY the same time of burn-out of their fuel (what a coincidence... I doubt IRL thats correct), and this is 10 seconds. Apart from that, only thrust and drag values can alter their range, if we count on a non-maneuvering target, and we don't count in loft trajectory, which differences would be enough to give the mentioned advantages to the amraam.

[GGTharos]

There is not reason for this to not be correct, actually - it is a reasonable ballpark. You can't expect ED to acquire exact motor burn times for everything, they just do the best they can. The R-27ER is undoubtedly the draggier missile with the bigger rocket. It does not implement energy preserving measures on the level than the AIM-120 does, which is why the 120 performs better. Newer missile, newer techniques, newer and constantly updated rocket motor - it's just a newer, better thing.

 

The encyclopedia in-game is out of sync with updates that go into the game unfortunately; and generally speaking missile ranges are adjusted based on the most credible source of info that can be found plus educated guesses where needed.

 

One thing I'd comment on this - I've tested, and the AIM120C and R27ER hase EXACTLY the same time of burn-out of their fuel (what a coincidence... I doubt IRL thats correct), and this is 10 seconds. Apart from that, only thrust and drag values can alter their range, if we count on a non-maneuvering target, and we don't count in loft trajectory, which differences would be enough to give the mentioned advantages to the amraam.

Edited December 3, 2012 by GGTharos

[159th_Viper]

OT posts removed.

 

Bug thread, Gents. Bug thread.

[IvanK]

Rmax Tracks.

 

In the ZIP 2 tracks from the same basic setup re flown today. Head on 7000m C17 as target. Closure 830Knots/1540Kmh

 

Tracks illustrate respective Rmax values. Russian Rmax track also documents the STT Russian Fire zone bug.... watch R73 values esp post lock. So all issues in single track.

 

Values I got in these tracks are:

 

AIM120C

Rmax1 34nm (42Km)

Rmax2 19nm (25.9km)

 

R27ER TWS ACQ Cursour over tgt

Rmax1 55Km (38nm) Post STT 38km

Rmax2 19Km (21nm) Post STT 21km

 

R77 TWS ACQ Cursour over tgt

Rmax1 40Km (21.6nm) Post STT 38Km

Rmax2 14Km ( 7.6) Post STT 21km

 

R73

Post STT Rmax1 jumps to 38Km

Post STT Rmax2 jumps to 21Km

RmaxTracks.zip

Edited December 3, 2012 by IvanK

[159th_Viper]

/OT posts removed to separate thread.

 

http://forums.eagle.ru/showthread.php?t=98568&page=3

 

THIS..........IS..............A...............BUG..................THREAD!

[Cali]

Rmax Tracks.

 

In the ZIP 2 tracks from the same basic setup re flown today. Head on 7000m C17 as target. Closure 830Knots/1540Kmh

 

Tracks illustrate respective Rmax values. Russian Rmax track also documents the STT Russian Fire zone bug.... watch R73 values esp post lock. So all issues in single track.

 

Values I got in these tracks are:

 

AIM120C

Rmax1 34nm (42Km)

Rmax2 19nm (25.9km)

 

R27ER TWS ACQ Cursour over tgt

Rmax1 55Km (38nm) Post STT 38km

Rmax2 19Km (21nm) Post STT 21km

 

R77 TWS ACQ Cursour over tgt

Rmax1 40Km (21.6nm) Post STT 38Km

Rmax2 14Km ( 7.6) Post STT 21km

 

R73

Post STT Rmax1 jumps to 38Km

Post STT Rmax2 jumps to 21Km

 

Rmax on the R77 at 21 miles :huh: and the R73 :huh::huh: nice test. Doesn't the in-game tact reference say the Er should have a 70km range?

[Weltensegler]

What flyable are you referring to? And what exactly do you mean when you say that there are no key assignments but then say that there are? ([ and ])

 

What is 'Radar Range'?

 

The complete bug list is repeated every couple of pages so there is no need to wade through 63 pages - jut page back until you find the list.

 

Sorry for being unspecific. Doesn't seem to be in the list yet.

I am talking about ALL flyables.

The displayed range of the radar can be toggled by pressing "[" and "]" which in the F15 can also be done by hitting upper or lower edge of the display with the target designator.

But this default assignment does not show up in ANY control assignment in my installation which means I can't assign it to a MFD(hardware) button in order to not have the keyboard on my lap when sitting in the cockpit.

 

Easy to check...go in options-controls and push any key and the list/highlight will jump to that key and its assignment.

Now press "[" and nothing will happen.

If it does then only my installation is f***ed.

 

cheers

[lennycutler]

Perhaps I don't understand your issue....for my F15C setup, the display zoom in and out "- and + " keys are mapped to my Warthog Throttle, which increases or decreases the displayed range of the radar.

 

Pressing the keys "[" and "]" has no function. I believe the "+" and "-" keys are the default for display zoom in and out for all flyables in FC3.

[Kuky]

The displayed range of the radar can be toggled by pressing "[" and "]" which in the F15 can also be done by hitting upper or lower edge of the display with the target designator.

 

But this default assignment does not show up in ANY control assignment in my installation which means I can't assign it to a MFD(hardware) button in order to not have the keyboard on my lap when sitting in the cockpit.

 

Ok, this is not a bug and you can assign any key command to your MFD button. It's true not all key assigments are visible for all controllers by default, but you can change this easily by clicking on any controller button in game Input options and click on top to clear all controller assignments.. that will automatically create all keyboard assigments for that controller... then you can assign to that controller anything you want, that's in the keyboard assigment list.

 

PS: in case you used old input files from previous versions delete them and let the game create new ones.. then do as above and you'll be able to assign radar range commands to MFD buttons.

Edited December 4, 2012 by Kuky

[Weltensegler]

ok I just went in and it is - and = indeed...yesterday I swear it was [ and ]!

I wasnt drunk! Was using [ and ] for hours.

So why ever that changed yesterday for me its probably not a common bug, so never mind and sorry for polluting the thread!

 

and thank you for the tip Kuky!

[combatace]

Other flights keeps on saying 'engaging bandit' and 'tally bandit' even a minute after all bandits were destroyed (not the wing-man).

 

Wing-man declares bingo fuel after landing, parking and turning off his engines.

 

Here is the track.

chatter.trk

[159th_Viper]

 

Values I got in these tracks are:

 

AIM120C

Rmax1 34nm (42Km)

Rmax2 19nm (25.9km)

 

R27ER TWS ACQ Cursour over tgt

Rmax1 55Km (38nm) Post STT 38km

Rmax2 19Km (21nm) Post STT 21km

 

R77 TWS ACQ Cursour over tgt

Rmax1 40Km (21.6nm) Post STT 38Km

Rmax2 14Km ( 7.6) Post STT 21km

 

 

Couple of questions:

 

Re R27ER TWS Rmax2 19Km (21nm)?

 

Should be 40km, yes (21nm)?

 

Also, conclusions from this test? Why should X not outrange Y etc etc?

 

Forgive the request for clarification, but I do not want to assume/infer :)

[IvanK]

Couple of questions:

 

Re R27ER TWS Rmax2 19Km (21nm)?

 

Should be 40km, yes (21nm)?

 

Also, conclusions from this test? Why should X not outrange Y etc etc?

 

Forgive the request for clarification, but I do not want to assume/infer :)

 

 

Typo conversion finger stuff up on my part.

 

R27ER Rmax 2 TWS 19Km or 10.3nm

 

As to conclusion well just my opinions based on unclassified sources and general scuttlebut. I believe the R27ER should be slightly better in the Rmax1 department than the AIM120C ... but not by much. The R27ER should have the advantage in a 120 in the face shoot out maybe in terms of range .. but loses out in that the pilot needs to support the missile all the way to impact. Missile speeds I have not really looked at so a faster 120C (if it really is) may actually get there first even if fired at the lower range. To me anyway online its no contest the AIM120 will always get there first ... thats my experience (on the receiving end).

 

I am sure that you guys in ED have better references on hand than myself.

 

The really high priority imo is to get the Russian Fire zone computation and display fixed .. its kind of unusable at the moment. Clearly the TWS displayed ranges seem reasonable. STT ranges on the other hand are just weird.

[159th_Viper]

I believe the R27ER should be slightly better in the Rmax1 department than the AIM120C ... but not by much. The R27ER should have the advantage in a 120 in the face shoot out maybe in terms of range .. but loses out in that the pilot needs to support the missile all the way to impact.

 

Concur.

 

The really high priority imo is to get the Russian Fire zone computation and display fixed ...

 

Already sorted. Just exited that very test before I typed here :)

[GregP]

Is it just me, or are the HUD indications of having AIM-120s or AIM-7s selected a bit off? According to the manual you should see, in the lower left corner, either "120C X" or "7M X" where 'X' is number remaining. But I'm seeing something more like "A8L" and "S4M" or something like that.

[GGTharos]

The current in-game indications are the correct ones.

[combatace]

HSI of Su-33/27 has alignment problem with day and night textures.

 

 

Flags are bit off too

[IvanK]

F15 Radar elevation altitude coverage indication incorrect ?

 

In FC3 Radar elevation scan coverage at TDC range is displayed on the left border of the scope in RWS. Should it not just be 2 data blocks at the top left of the scope ? Then in STT 9Or TWS on the PDT) it becomes a single Tgt alt value alongside the elevation caret ?

 

 

Edited December 5, 2012 by IvanK

[Gaanalma]

it's quite lot of work to keep everything up to date so frequently, I think Viper is actually doing a very good job keeping track of the list. Little checking on previous 2-3 pages doesn't hurt does it? :smilewink:

 

 

I was just saying because in this way you could save the answers to people who are not following the topic ... I am convinced that Viper is doing a great job and for me it is a pleasure to see her updates, I just hate to see that laziness of some, Viper gets loads of frustration ...

 

Thank you guys!

[RIPTIDE]

@Viper: The new dynamics for friendly sams activating when bandits are near and giving mud nails to friendlies ALSO occurs in the absence of bandits when friendly SEAD missiles are fired in the general area.

 

EDIT: Is this a World or FC3 bug? Or is it a bug really?

Edited December 6, 2012 by RIPTIDE

[GGTharos]

World ... something. You should always pick up friendly SAMs; a long time ago this was eliminated in an effort to eliminate some of the random friendly fire from SAMs, IIRC.

[Maraudeur]

@Viper or GGTharos: many issues were raised on this topic that were said not to be this topic related. Could you then tell us on wich topic we ought to report these issues (such as AI aircraft lately activaated not having ejection seats inside untill aircaft is trigger activated)

Than you

[IvanK]

F15 HUD BUG

 

What are the bottom row of numbers in the HUD data block under the Airspeed tape, they are there in all modes ?

 

 

 

These should be Own aircraft G I believe ?

 

Also I notice that passing around 20units AOA Mach number is replaced by AOA XX is this correct ?