Bug List

[KILSEK]

Hi all.

 

Has any noticed the when using easy radar on the A-10, the Mav's do not constantly update the distance to target? I usually see a 0.0 distance or a constant (for example) 4.7 Mi that stays that way even as I approach. I usually switch weaps, modes and targets (switching back to the original) to get a updated distance to target. I want to report it so that if it is a bug a fix may make it into the patch. -KILSEK

[berkoutskaia]

2 BBQ, about this graphic "bug": look at your graphics.cfg file. My guess is that you tweaked that one a little... Try to restore default settings.

[169th_Dredd]

Not sure if this is a bug, maybe someone can confirm it.

When locking a target in EOS, he recieves no warning on his RWR(correct function).

Then directly pressing 'I' to SCAN radar mode whilst still locked, the target should recieve a lock warning on his RWR, yet he receives no warning.

 

Is this because EOS mode is still active, yet I've switched to SCAN BVR directly from EOS(pressing 'I')?

 

Whilst flying with a team member we both tried this, and had the same thing occur. We were both flying Mig29's within visual range.

 

EDIT: My apologies, I see Goya already mentioned this.

[BBQ]

Another Graphic Problem--Weapons not fully rendering

 

%5Bimg%5Dhttp%3A//i3.photobucket.com/albums/y83/brandtryan/ScreenShot_001.jpg[/img]

[BBQ]

2 BBQ, about this graphic "bug": look at your graphics.cfg file. My guess is that you tweaked that one a little... Try to restore default settings.

 

Berk--I haven't tweaked anything (yet)--not that familiar with mods for this title! I did a clean install of LOMAC, then right to FC, then Season Pack.

 

I posted another graphic glitch on my weapons not fully rendering off the wing--

[169th_Dredd]

Berk--I haven't tweaked anything (yet)--not that familiar with mods for this title! I did a clean install of LOMAC, then right to FC, then Season Pack.

 

I posted another graphic glitch on my weapons not fully rendering off the wing--

 

 

BBQ, looks similar to what happens when you Alt-Tab out and back into game.

Also I've found problems with certain video card drivers with lock on graphics not working correctly.

 

I suggest trying out lower versions of video card drivers. Just a suggestion. ;)

[D-Scythe]

User-made Campaigns keeps crashing on me. The only way to fix it is to go in, tinker around uselessly a bit, then re-saving and see if it works - usually it takes like 5 saves. Really, really annoying.

[Greco]

BBQ....You need to set VISIB RANGE in the GRAPHICS options to MED or HIGH. I get the exact same graphical anomalies as you if I set VISIB RANGE to LOW.

 

Hope this help you,

 

Greco

 

P.S. I am using the Cat 5.4 drivers. I saw the graphical glitches that you posted using the Cat 5.1 and Cat 4.12 drivers. Solution always was to set VISIB RANGE to MED or HIGH.

[S77th-GOYA]

The bug that causes the radar to stop scanning in the 15 seems to happening more often. My guess is it is caused by cycling radar off and on, as this is what I did tonight right before I noticed it had stopped scanning. I turned it off to clear ghosts and when I turned it back on there was nothing there.

[BBQ]

Thanks Greco!

 

BBQ....You need to set VISIB RANGE in the GRAPHICS options to MED or HIGH. I get the exact same graphical anomalies as you if I set VISIB RANGE to LOW.

 

Hope this help you,

 

Greco

 

P.S. I am using the Cat 5.4 drivers. I saw the graphical glitches that you posted using the Cat 5.1 and Cat 4.12 drivers. Solution always was to set VISIB RANGE to MED or HIGH.

[169th_DedCat]

The bug that causes the radar to stop scanning in the 15 seems to ... caused by cycling radar off and on.

 

I think just about anyone who has driven the Eagle in LOMAC for any length of time has experienced this bug. I'm sure a lot of people just don't notice it when it is happening because they may not recognize when the radar antenna carets stop moving.

 

To me it seems not only linked to switching the radar on and off, but some sort of combination of that and the AACQ modes, especially the Gun AACQ mode. Something about switching in and out of that mode, turning the radar on and off, and possibly even switching in and out of NAV mode in the improper way triggers the bug. I've never nailed down the key combination that causes it, but I try to avoid it as best I can by using the AACQ modes in as predictable a manner as possible.

[GGTharos]

I've experienced this bug VERY rarely in 1.1, and going to VS, then back to BVR has typically fixed it for me without the need to bot out of the game.

[169th_DedCat]

I've experienced this bug VERY rarely in 1.1, and going to VS, then back to BVR has typically fixed it for me without the need to bot out of the game.

 

I have experienced it in at least three occasions so far, and switching from VS to RWS or anything else never fixes the problem. The only solution for me is and has always been to eject and get a new bird.

[Prophet_169th]

Just to note, the bug where you cant adjust the height of the F15 radar, is fixed by switching to NAV then back to BVR.

 

Thanks Dedcat for that fix.

 

I would also like to note, the Su25T cockpit isnt fully 'rendered' I guess you would say.

If you look at the back of the sides of the cockpit, its just gray. But if you look from the F2 view, there should be a lot more room to look back at.

[Prophet_169th]

I've experienced this bug VERY rarely in 1.1, and going to VS, then back to BVR has typically fixed it for me without the need to bot out of the game.

 

I had this bug last night. Nothing fixed it. I never eject if not needed, so I just for it with AIM120 in Visual, and AIM7 in Flood. Until I die that is =D

 

Death before dismount!! And that has more meaning for a pilot LOL!

[S77th-GOYA]

I have experienced it in at least three occasions so far, and switching from VS to RWS or anything else never fixes the problem. The only solution for me is and has always been to eject and get a new bird.

 

I've also found GG's suggested fix useless. Between my wingman and me, this bug has occurred roughly 8 times since 1.1 was released. That is much more frequent than 1.02.

[golfsierra2]

The bug that causes the radar to stop scanning in the 15 seems to happening more often. My guess is it is caused by cycling radar off and on, as this is what I did tonight right before I noticed it had stopped scanning. I turned it off to clear ghosts and when I turned it back on there was nothing there.

 

What a lousy radar, never saw any 'ghosts' on my N-019M Topaz....

 

MiG29S rulez !

[169th_DedCat]

I had this bug last night. Nothing fixed it. I never eject if not needed, so I just for it with AIM120 in Visual, and AIM7 in Flood.

 

I don't think the AIM-7's flood mode works when this bug occurs since the radar seems to not only stop scanning up/down and right/left, but it seems to stop transmitting entirely.

[S77th-Souless]

When in flood mode with the aim 7 the radar is focusing its entire energy within the relative circle on the hud ive never seen it scan in this mode.

I dont believe it does but i might be wrong.

When the radar locks up your best stopping the game because i can never get it to start back up again.

Read goyas post above and it happens more frequently

[169th_DedCat]

When in flood mode with the aim 7 the radar is focusing its entire energy within the relative circle on the hud ive never seen it scan in this mode.

 

I realize... my point was that when the scanning bug occurs in the Eagle, the radar not only stops scanning, it stops transmitting entirely.

[Prophet_169th]

Nope, flood works great. I have had great success when the radar goes to crap, and using flood. I actually seem to get more kills, since I aint flying high with it all hanging out.

[Guest EVIL-SCOTSMAN]

Communications menu not working.

 

I know I mentioned this one earlier but since then I've done some testing and maybe ED can look into it.

 

I've reinstalled FC on a different computer and still have the same problem.

 

The first pc is a Intel P4 3.6Ghz, Intel 925 Motherboard, Radeon X850XT PCIE video card, running windows XP Pro SP2, 2 GIG RAM, 2 x 80G Maxtor HDD (Raid 0)

 

Second PC: P4 3.2 Ghz, Intel PERL865 Motherboard, Radeon 9800XT, 2GIG RAM, 2 x 80G Maxtor HDD (Raid 0)

 

Peripherals (for both) CH Products Pro Throttle and Fighterstick USB, Microsoft cordless keyboard and mouse, Track IR 1, CTX 19" LCD Monitor.

 

I can map any key to "Communication menu" and problem still exists.

 

If I Alt-Tab to Desktop then back the "Communication menu" will work for a short period of time maybe 2-3 minutes then it stops working again.

 

I hope that ED can reproduce this problem, I find it hard to believe I will be the only one having such dramas considering It's "Industry Standard" hardware and happenning on two different machines.

 

I've also downloaded the Addon a second time to no avail.

 

ragards,

 

 

exactly same problem as i am having, alt tab out and then in again, it works for about 2 minutes it then stops workin again or just wont even appear when i push the key to bring up the menu

[Ice]

I narrowed it down to Microsoft Wireless Keyboard / Mouse Combo Scotty.

 

Is that what you have ?

[Guest EVIL-SCOTSMAN]

nope, standard ps2 keyboard and usb mouse, wish it was the same as urs, cuz then id know what is causing it... :confused: :(

[Wags]

Regarding ARH sytems not going after the designated target, have you guys tried this with non-jamming aircraft? I ask because I just did several tests of rapid fire TWS shots on 4 - 6 non-jamming targets (Il-76) at various spacings and altitudes and had no problems. Worked quite well in fact.

 

My guess is that jamming aircraft are trashing the missiles' lock while not breaking the lock of the supporting aircraft. Hence, the missile is looking for the best RCS target out there, while the user thinks the missile should still be guiding towards the intended target. Just a hunch.

 

The far too large seeker FOV is just making things worse.

 

-Matt