Bug List

[169th_DedCat]

So when a missile is launched from a high altitude or low altitude in respect to your aircraft, you will not hear a launch tone?

 

If the difference is more than 30 degrees from your centreline for the Russian aircraft, or 40 degrees in the U.S. aircraft, yes. No launch or lock tone. It's in the manual.

[169th_DedCat]

So, is anyone else absolutely LOVING those 90 deg gimbals on the 77 and 120? :D

 

Heh, no... that problem has been around since 1.02. The all seeing maddog. Ice posted a thread in here about it complete with tracks demonstrating it a while back.

[169th_Crusty]

HeHe das what I thought. But TomAce promised me he has an ILS in his HUD LOL

 

The ILS on the HSI works perfectly every time. ADI needles seem to be linked

to the director circle in the HUD. Now... the ILS circle in the HUD - I`ve been

told that it works flawlessly :/

I`ve done crapload of carrier approaches from different setups, intercepting the ILS at various distances (within ILS range) and sometimes the small circle

was not where I would expect it to be. I was constantly comparing it to the

needles on HSI (not ADI). Well, wether it works properly or not... I use the

HSI and it gets me a "OK" 3 wire everytime (almost everytime ;))

[berkoutskaia]

Well, it looks like the russian fighters have been granted an Air-ground radar !!!

 

Just kidding ;), but the bug I report is a serious one imo:

 

First, AWACS still see through mountains, but well, I'm used to it. But now AWACS can see any aircraft taxiing !!! I really have no idea about AWACS radar capabilities, but this really is strange...

 

Second, when flying towards such a contact (not knowing it is a taxiing A/C), I switch radar on at about 50 km, see 2 strong jamming strobes, then burn through, lock one of them, and here's what I see:

 

 

Target F-16, altitude 0 above ground, speed 10 km/h, Launch Authorized.

 

It seems really unlikely that the Flanker's radar can have suc A/G features, isn't it?

[berkoutskaia]

I've been through further testing about this one, it looks like it happens only on A/C with jamming on (and by the way, I don't think it's that good to have music on while on the ground :D).

 

You may want to watch this track to see what I'm talking about:

[Guest Cali]

The ILS on the HSI works perfectly every time. ADI needles seem to be linked

to the director circle in the HUD. Now... the ILS circle in the HUD - I`ve been

told that it works flawlessly :/

I`ve done crapload of carrier approaches from different setups, intercepting the ILS at various distances (within ILS range) and sometimes the small circle

was not where I would expect it to be. I was constantly comparing it to the

needles on HSI (not ADI). Well, wether it works properly or not... I use the

HSI and it gets me a "OK" 3 wire everytime (almost everytime ;))

 

I line my circles up and land perfectly everytime. My first landing I had no idea about them and needless to say I landed but broke both my wings. Since then I have had 3 sucessful multiplayer landings with no problems or broke wings.

[169th_Moose]

I line my circles up and land perfectly everytime. My first landing I had no idea about them and needless to say I landed but broke both my wings. Since then I have had 3 sucessful multiplayer landings with no problems or broke wings.

 

ILS? Only time I use them is in bad weather or Night missions. If I have a visual on carrier. Then is no longuer required. LOL but that just me. ;)

[Guest Cali]

ILS? Only time I use them is in bad weather or Night missions. If I have a visual on carrier. Then is no longuer required. LOL but that just me. ;)

 

I can eyeball it just fine 90% of the time, it's the other 10% that gets me. But the circles are very easy to use and lets me touch down with no problems.

[Russianfish]

Having a wildly inaccurate HSI 9 times out of 10 is a FEATURE?! Let's be serious, if you're going to model something silly like that than you have to give the user the ability to manually readjust the HSI for a correct bearing. As far as I know there is absolutely no way to do that currently.

 

All this feature has done is effectively made the HSI useless. Any navigational instrument that is regularly off by as much as this gauge now is in the Frogfoot would certainly ground the aircraft. A realistic drift is something on par of a couple of degrees or so.

 

While you're at it, why not add the ability to manually adjust the course needle too?

 

 

This has me puzzled as well, modeling a problem without a proper soloution? If its a feature then please make the HSI adjustable.

Although one way around it is switching to weapons mode then back to Nav, it resets on course to WP 1.

[LawnDart]

The formation lights turn off on the F-15 at night when you get close enough in formation on another plane in multiplayer. While you're far away they stay on. Your own lights appear turned on all the time (as long as your in nav mode). I'd call this a bug!

 

LawnDart

[Ironhand]

Having a wildly inaccurate HSI 9 times out of 10 is a FEATURE?! Let's be serious, if you're going to model something silly like that than you have to give the user the ability to manually readjust the HSI for a correct bearing. As far as I know there is absolutely no way to do that currently.

 

All this feature has done is effectively made the HSI useless. Any navigational instrument that is regularly off by as much as this gauge now is in the Frogfoot would certainly ground the aircraft. A realistic drift is something on par of a couple of degrees or so.

 

While you're at it, why not add the ability to manually adjust the course needle too?

 

Out of curiosity, do you see this problem both with a hot start on the runway and a cold start on the tarmac? In the latter scenario, the sim models gyro spinup. In real life, you need to sit in place for 9 minutes (I think that's the amount of time) to give the gyros time to stabilize. While I haven't tested this extensively, it seems to be the case that the sim models this but shortens the waiting period to 3 minutes.

 

So, if you are entering the cockpit, starting engines, and rolling as soon as you have any measure of thrust, you're going to have problems.

 

Rich

[Ironhand]

A small bug: Inaccurate barometic altimeter setting when starting on the runway.

 

If you start on the tarmac (apron), the barometric altimeter has the correct setting for the aerodrome's altitude. But, if you start on the runway, the barometric altimeter is set to sea level.

 

Rich

[ZoomBoy27]

A small Mission Editor error:

 

When you chose an Aircraft or Helicopter flight, the HIDE label does not appear next to the Button.

It does for Static Objects and Ground Vehicles

[169th_Crusty]

Out of curiosity, do you see this problem both with a hot start on the runway and a cold start on the tarmac? In the latter scenario, the sim models gyro spinup. In real life, you need to sit in place for 9 minutes (I think that's the amount of time) to give the gyros time to stabilize. While I haven't tested this extensively, it seems to be the case that the sim models this but shortens the waiting period to 3 minutes.

 

So, if you are entering the cockpit, starting engines, and rolling as soon as you have any measure of thrust, you're going to have problems.

 

Rich

 

9 min? - Are you talking about the Inertial Nav system line up?

The HSI should work independently of the INS. It is pretty much a backup

instrument in any modern jet and its own gyro takes no more then couple of

minutes to fully spin up. Regardles of that, it can always be manually (or otherwise) re-alligned at any time.

[169th_Moose]

Real Annoying Bug, respawning over water, then my game crash. sorry for posting full size, I dont know how to make thumbs nails in here. Also other bug I notice, the respawn fonction allow multiple respawn under the main point. Causing crash, due that 2 birds attempt to respawn on the same time... most noticable on the carrier.

 

http://169thpanthers.net/main/modules/pnCPG/coppermine/albums/userpics/10122/ScreenShot_107.jpg

 

did not want to spawm dialup users with this pic so just attach the link.

 

Make note that this bug has followed trough 1.00, 1,01 & 1.02

[S77th-Souless]

Try this take a mig 29 go to vertical scan mode you will pick up a target at 40km what is up with that?

this is in multiplayer, jesus

[Kula66]

Remember that the missile chooses its target based on radar signature for the ARHs, not based on what you're illuminating or designating - but I consider this to be slightly wrong, ie. the datalkink/illumination should play a role in ensuring that the weapon attacks the desired target. Once the datalink is lost, however...

 

Is this something you as an ED Tester can get confirmation on GGT? To me this negates the use of multi-shot engagement for the F-15 ... its not a major issue on-line when you tend to go 1 v 1 ... but this has got to be wrong and NOT how it worked in 1.02 - why was it changed? Or is it a bug.

 

Thanks,

James

[169th_DedCat]

F-15 Iff

 

(edited after Kula66's reply)

 

I had thought there was no IFF in TWS for the F-15, however it looks like I was wrong and that the symbology is there in TWS, but it is extremely faint for some strange reason.

 

However, there still is no way to IFF in STT outside of using the NCTR, which is insufficient when fighting in an environment where the same plane may be found on either side.

 

Here's a scan from an old Jane's manual for reference. Yes this is the APG-70 in the F-15E, but I'm just using it to demonstrate the symbology here. Note the part about a friendly designated target flashing from circle to star.

[Kula66]

I'm a little disappointed this issue wasn't addressed in 1.1, so I'm adding it to the list here again.

 

The F-15's radar will not IFF unless you are in RWS. In TWS and STT you have to rely on the NCTR to identify a target, which is insufficient when fighting in an environment where the same plane may be found on either side. Why can't the little circles or rectangles we see in RWS be ported over to TWS and STT too?

 

Here's a scan from an old Jane's manual for reference.

 

Dedcat, I think they are in TWS mode ... they are just faint and nearly impossible to read reliably ... on-line, I usually switch to RWS mode, then back to TWS to check (with the inherent risk of not being able to re-acquire) or zoom right into the screen. I thought the HUD should show a big X if the target was friendly ... It needs to be fixed.

[169th_DedCat]

Dedcat, I think they are in TWS mode ... they are just faint and nearly impossible to read reliably

 

Hmm... looks like you're right, but they are ridiculously faint. There is no reason they need to be that faint.

 

I know there certainly is no big X on the HUD when you have a friendly in STT. There really needs to be something of that nature, because transitioning to RWS to IFF when you're in close and using your AACQ modes is not a serious solution. See my now edited above post and attachment about the PDT "mipple" when a friendly is designated.

[Kula66]

I've got some video showing a big X when the gun piper is active, but I'm not sure if this is a symbol for friendly or not ... the next frames show the target exploding so I'm not sure .... anyone know any F-15 pilots?

 

IFF is a real pain on servers where you fly Isr v US or Su-27 on both sides ... I try and avoid these if poss ... now with the mixed 1.02 and 1.1 servers this will be more difficult!

[Asterix28573]

Hi,

IIRC, the big X on HUD warns the pilot that he's about to crash if he doesn't change course. It appears i.e. when performing a dive and dangerously getting near the ground. There's also a warning sound, I think.

 

This is at least what happens in the F-16 according to F4 manual, but I assume that for the F-15 is probably the same.

 

Cheers,

Asterix

 

 

 

I've got some video showing a big X when the gun piper is active, but I'm not sure if this is a symbol for friendly or not ... the next frames show the target exploding so I'm not sure .... anyone know any F-15 pilots?

 

IFF is a real pain on servers where you fly Isr v US or Su-27 on both sides ... I try and avoid these if poss ... now with the mixed 1.02 and 1.1 servers this will be more difficult!

[Kula66]

No this is A2A with sky all around ... may indicate inside missile range BUT it has the gun piper on screen ...

[S77th-GOYA]

Remember that the missile chooses its target based on radar signature for the ARHs, not based on what you're illuminating or designating - but I consider this to be slightly wrong, ie. the datalkink/illumination should play a role in ensuring that the weapon attacks the desired target. Once the datalink is lost, however...

 

If that was true, every 120 shot would be a maddog shot with no reason to lock anything.

[GGTharos]

It is true; the issue here is that the parent aircraft undoubtedly communicates which target it is to look at after launch, whereas in LOMAC this isn't happening. The ARH's are radar silent until they get within 'optimal killbox scanning' range ... the problem here is that in LOMAC the ARHs grab whatever they want, whenever they want it, instead of diong 'snap looks' in the direction of the chosen target(s) or searching the target's killbox should the target be lost. It's an issue with how seeker logic is programmed, no doubt.