FC2 Bug Thread

[EvilBivol-1]

Any one else having this issue with the A10 I take off and the climb ladder is left of center. On any mission I do. It seems to be something with the track ir. All the other planes no problem just the

A10 is doing it.

I saw one user on the Russian forum report the same issue and have it fixed by updating his (nVidia) video drivers.

[Distiler]

I saw one user on the Russian forum report the same issue and have it fixed by updating his (nVidia) video drivers.

 

It also happened to me in some occasions and I thought it was due wind.

[jalebru]

Not sure if this has been posted, in the Mig-29G pit, the Hud lists range to next waypoint in KM, but the HSI lists it in Miles.

[Fahhh]

I seem to experience a weird problem. I took off(in MiG-29S), and everything was working. Then sometime into the mission, only the control axis seemed to respond, the keyboard and the joy buttons(which through Saitek SST are assigned to keyboard inputs seize to work). I needed to Alt+Tab out and then back to the game to regain full control. Happened on a MP flight in 104th Dedicated 30 mins ago, then I decided to try a flight in the quickstart missions - MiG-29S, and it happened again. I can control the axis, but button inputs are not working. The weird thing is that I have more than 10 flights in the MiG with the current control setup and hadn't experienced this problem...

 

Win7 64, Russian FC2

[JasBird]

In the mission briefings for the Mig 29 missions it says I-RWIN to change frequency, but on keycard it says I-RShift which is correct. I also get a big decrease in framerate when I toggle on the full infobar. Just the framerate is fine, but when I get all the memory info I go from 30 fps to about 10. Didn't happen in BS.

 

Had Catalyst AI enabled, seems that was reason for drop in framerate.

Edited April 7, 2010 by LeadBird

[Fahhh]

I seem to experience a weird problem. I took off(in MiG-29S), and everything was working. Then sometime into the mission, only the control axis seemed to respond, the keyboard and the joy buttons(which through Saitek SST are assigned to keyboard inputs seize to work). I needed to Alt+Tab out and then back to the game to regain full control. Happened on a MP flight in 104th Dedicated 30 mins ago, then I decided to try a flight in the quickstart missions - MiG-29S, and it happened again. I can control the axis, but button inputs are not working. The weird thing is that I have more than 10 flights in the MiG with the current control setup and hadn't experienced this problem...

 

Win7 64, Russian FC2

 

Found a workaround possibly for the same problem:

 

http://forums.eagle.ru/showthread.php?t=52360

[coder1024]

Found a workaround possibly for the same problem:

 

http://forums.eagle.ru/showthread.php?t=52360

yes, that workaround solved the problem for me. you can either tap RCtrl again by itself after chatting or re-map team chat to something which doesn't use a modifier.

[71st_Mastiff]

No I have tried diffrent Nvidia drivers same issue and still only with the A10 has something to do with track ir, settings.

I'm using the new 5.0 track ir with the pro 4 so Ill roll back to track ir 4 software and see if that works.

Edit; didnt make a diffrence still same only the A10 is effected.

Edit: Ok turned off the wind and the ladder is straight and level but should'nt the Avionics computer take this into acount like in the F15?

It also happened to me in some occasions and I thought it was due wind.

Edited April 8, 2010 by Mastiff

[Grimes]

Strange bit of rendering for whenever a missile hits a ship. The water splash isn't rendered at the water line. It looks as if it treats where it first contacted the ship as the water line and renders the corresponding splash effect at the same location.

[104th_Crunch]

FC2: Long brief of MP mission causing bug

 

Not a serious issue, but I thought I would share.

 

Halcyon was nice enough to write an interesting back story for out new mission running on the 104th. I added it to the our mission briefing and it caused the following errors; in the MP server browser, the mission name was blank and displayed pings of +500000ms

 

Is there a maximum to the briefing size?

 

Will longer briefs cause server instability?

 

Thanks

 

A copy of the same version of the mission, one with a short brief and one with a long brief attached.

104th Operation Liberty 10 Short Brief.miz

104th Operation Liberty 10 Long Brief.miz

[Panzertard]

I'll test your mission on my server to see if happens here - if it does I'll report it asap.

EDIT: Ah, FC2. Still checking - brb.

Edited April 8, 2010 by Panzertard

[Panzertard]

By the looks of it yes - I'll report it.

[Downey Jr.]

I posted this in a thread but the rockets release from the A-10 is EXTREMELY sensitive and causes you to lose your entire load instantly...

 

I heard others have this issue...what's the deal? I'd like to fire a moderate or pick the number of rockets I fire

[S77th-konkussion]

Awacs vector to tanker is mostly way off. Can call for it 3 times or more in succession and get wildly different calls. (both bearing & range) The only discernable pattern to this is it seems to behave this way for a bit after taking off. Few minutes later- it works fine.

 

Took some screens just prior to carrier touchdown. Wingman confirms he saw the messages. None of them appeared in the folder. 7 screens from a prior session in there now

[PoleCat]

Good find Crunch.

 

Out

[104th_Crunch]

By the looks of it yes - I'll report it.

 

Thanks for reviewing it.

[159th_Viper]

I posted this in a thread but the rockets release from the A-10 is EXTREMELY sensitive and causes you to lose your entire load instantly...

 

I heard others have this issue...what's the deal? I'd like to fire a moderate or pick the number of rockets I fire

 

No Deal - Not a Bug ;). Likely culprit is your HOTAS programming technique/software.

 

Track from A10 Quick-Start Mission:

 

Rocket Allocation: 38 (2x19 Hydra Pod)

 

Salvo #1: 4 Rkts

Salvo #2: 4 Rkts

Salvo #3: 4 Rkts

Salvo #4: 4 Rkts

Salvo #5: 6 Rkts

 

Rockets left after Engagement: 16

 

Track: [ATTACH]37798[/ATTACH]

 

Addendum: Remapped 'Weapons Release' to Single Keypress with 'Hold' modifier on my system.

[Distiler]

F10 map only works IF you set external views ON. Should be independent, for example external view OFF and F10 map available.

 

Also, in the case of setting the minimal F10 map, where you can't see any object even your own aircraft, you can still click "me" and the map will center on you. I think "me" shouldn't work in that setting.

[Downey Jr.]

No Deal - Not a Bug ;). Likely culprit is your HOTAS programming technique/software.

 

Track from A10 Quick-Start Mission:

 

Rocket Allocation: 38 (2x19 Hydra Pod)

 

Salvo #1: 4 Rkts

Salvo #2: 4 Rkts

Salvo #3: 4 Rkts

Salvo #4: 4 Rkts

Salvo #5: 6 Rkts

 

Rockets left after Engagement: 16

 

Track: [ATTACH]37798[/ATTACH]

 

Addendum: Remapped 'Weapons Release' to Single Keypress with 'Hold' modifier on my system.

 

thanks man Ill check out the track... I tried many combos of presses and holds on the saitek software...I think found one that shot 4 rockets only I'm not sure I quite understand 'Weapons Release' to single keypress with Hold modifier...would you hold ralt and place the space key on single press without release?

 

 

*EDIT*

 

ok I figured it out...its all in the way you program your buttons...you need to go into advanced commends if you own a x52 and program in the press window the ralt-space VERY quickly...tap it you should have a .100 delay on the space release

 

this way you can release a pair of rockets!...not sure if this could affect anything else but dropping bombs there was no delay after pressing weapon release

 

not sure either if you can group more rockets or maybe just go with salvo mode (not tried that yet) but now you can easily release the least amount of rockets every time you fire

Edited April 8, 2010 by Downey Jr.
solution

[Downey Jr.]

ok last update gonna have to macro two versions of weapon release because mavericks wont fire with that quick sequence...

[akumai]

TWS + Manoeuvre + lock on crash

 

Hi there,

 

Been having this error quite a few times now but i've noticed it exclusively in multiplayer. Thats not to say thats the only times it happens, it just means i've been spending my time mostly online and thats when i've experienced it.

 

 

I'm using Vista 64 bit. The game crashes with a "simulater.exe" error etc when i'm performing a turn and my radar (F-15) is in TWS mode. All is ok until I slew to my intended target and attempt to lock on. Its at this point (hitting the lock target button) almost without fail the game crashes. Please find the attatched file which I hope will help.

 

Akumai/Fury/Shaheen

Error.zip

[topdog]

...

Took some screens just prior to carrier touchdown. Wingman confirms he saw the messages. None of them appeared in the folder. 7 screens from a prior session in there now

 

This will be due to permissions on the protected Program Files folder most likely, as MS don't like app developers writing user data there and developed data virtualization techniques to redirect the writes to another folder on your hard disk when using Vista/Win7/Win2K8 with all security enabled (including UAC).

 

They're doing this temporarily with 32-bit apps to give them a chance to still work on the new OS, but data virtualization won't be a long-term feature for MS to keep.

 

 

Given where Lockon is installed now, do Start -> Run -> %localappdata% (including the % characters) and then press Enter.

 

The folder that opens up should have another in it called VirtualStore.

 

Go in there, and then navigate through the directories as if you were trying to find where Lockon is installed to (Program Files\Eagle Dynamics\etc. etc.) until you find your missing screenshots.

 

This isn't a bug per se, unless Lockon was trying to get the MS Windows Vista/7 logo certification.

[Legolasindar]

I don't know if this is a bug.

With Shkval and TV of Maverick, if you fly leveled, TV Slew move well, but if you for example stay rolled 30 degrees, slew of TV not move well. Slew every move with the real horizon, not with TV horizontal. The natural human think is move right in the TV, not in the horizon, and this will be compensated by computer onboard. I think is rare movement is in FC because you can wath Shkval or TD Box (circle) in the HUD, but ever look Shkval when have this. The move by default can be realistic feature, but i down know.

 

I created two pictures for explain this.

 

 

 

And this is a BUG

When i set maximum zoom, Axis move wrong, Y axis is inverted.

Edited April 9, 2010 by Legolasindar

[Distiler]

I don't know if this is a bug.

With Shkval and TV of Maverick, if you fly leveled, TV Slew move well, but if you for example stay rolled 30 degrees, slew of TV not move well. Slew every move with the real horizon, not with TV horizontal. The natural human think is move right in the TV, not in the horizon, and this will be compensated by computer onboard. I think is rare movement is in FC because you can wath Shkval or TD Box (circle) in the HUD, but ever look Shkval when have this. The move by default can be realistic feature, but i down know.

 

 

And this is a BUG

When i set maximum zoom, Axis move wrong, Y axis is inverted.

 

First one I think it's ok, but not sure 100%. The nose camera moves right and left, perhaps the tv just rotates the image for the pilot when the aircraft rolls (the nose camera also rolls). Might be a bug tho, dunno really.

 

The second one, it works ok in my computer, whatever level of zoom I try (3 levels). I use keys.

Edited April 9, 2010 by Distiler

[Legolasindar]

The second one, it works ok in my computer, whatever level of zoom I try (3 levels).

 

I have Slew control assigned to Mouse, and control in Cougar with Microstick. You have same or use key pulsation?

 

Pues eso, que yo lo tengo asignado el Slew al mouse y lo controlo con el microstick del Cougar. No lo he comprobado, pero creo que con teclas funciona bien pero con eje no al maximo de zoom.