1.2.4 bug reports

[IvanK]

CCRP bug has been acknowledged by the devs.

[Robin_Hood]

Thanks, I didn't know, and a quick search through the forum didn't give me anything (apart from A-10C CCRP problems with wind).

[IvanK]

Thanks, I didn't know, and a quick search through the forum didn't give me anything (apart from A-10C CCRP problems with wind).

 

http://forums.eagle.ru/showpost.php?p=1738707&postcount=1133

[TX-EcoDragon]

I've just started to have blurry menu text. It looks almost like a heavy treatment of FSAA, except I don't use FSAA. I've only noticed recently. The text in the mission editor dropdowns is particularly hard to read.

[macieksoft]

I think that killed soldiers generating too much smoke while they start to burn after being hit (in this case by S-13 rockets).

 

They smoking just like oversized cigarette ;)

 

Its quite unrealistic and...

...And it is not fun because its killing my graphic card.

 

Edited May 17, 2013 by macieksoft

[Robin_Hood]

http://forums.eagle.ru/showpost.php?p=1738707&postcount=1133

 

Oh, I saw that one, but what I experienced isn't the same:

1. Bombs aren't released as soon as pickle is pressed. Instead, the timer counts down as expected, though bombes always fall short.

2. It does happen in the MiG-29, not only in the Su-27 (indeed, it happens in the Su-25T, which is why I posted in DCS World bugs in lieu of FC3 bugs)

 

But anyway, I'm sure the devs will look into it and work to fix it :thumbup:

 

macieksoft: Gosh, are you sure you didn't smother these guys with napalm ? :shocking:

[Cedaway]

I've just started to have blurry menu text. It looks almost like a heavy treatment of FSAA, except I don't use FSAA. I've only noticed recently. The text in the mission editor dropdowns is particularly hard to read.

 

I had that long ago:

Have you recently updated you graphic drivers?

If so and if it's ATI-AMD Gfx driver (catalyst), just double check your AA settings and be sure you're not on 'edge detect' filtering mode. Just leave the general settings on 'Use application Settings' and set the filtering option in DCS.

(Can't say for NVidia)

[Mustang]

I've just started to have blurry menu text. It looks almost like a heavy treatment of FSAA, except I don't use FSAA. I've only noticed recently. The text in the mission editor dropdowns is particularly hard to read.

 

Turn off Morphological anti aliasing in your CCC, the curved text is a dead giveaway.

[TX-EcoDragon]

I had that long ago:

Have you recently updated you graphic drivers?

If so and if it's ATI-AMD Gfx driver (catalyst), just double check your AA settings and be sure you're not on 'edge detect' filtering mode. Just leave the general settings on 'Use application Settings' and set the filtering option in DCS.

(Can't say for NVidia)

 

Turn off Morphological anti aliasing in your CCC, the curved text is a dead giveaway.

 

 

Thanks for the replies guys, but as I said, I'm not (intentionally) running any Full Screen AA (FSAA), though I agree that it looks just like it! Perhaps it's some conflict on my side. My CCC settings for AA are the defaults "App Controlled", "Standard", "Multisampling", and Morphologic filtering" is off.

 

 

[EDIT] RadeonPro seems to have been the culprit, even though I'd deleted the profiles in it, the Global profile needed to be reset. I've got no idea why it didn't impact other sims.

Edited May 19, 2013 by TX-EcoDragon

[f3n3k]

bug light with all airport on client side in multiplayer:

 

master side:(exemple vaziani)

 

spot on truck ok, but no leds on airport and parking

 

 

 

 

client side:

 

Leds ok on airport and parking but no spots...

 

 

Ka-50 on runway and confirmation by atc for take-off, but no spots on

 

 

 

Thanks and Cya

 

edit: it's a fresh install

Edited May 17, 2013 by f3n3k

[Speacy]

In editor, with -ARM missile type selected, the AI don't shoot AGM-88 on target (RADAR) and RTB, because of this we can't choose correctly the armament for this tgt type (auto mode use AGM-65 also )

[Angel101]

Something wrong with Aim-9M or A10C exhaust. Aim9M blocks in left wing of A10C, not behind the engines.

 

We tried to put in idle left engine an right to full power... the result was a direct hit on left engine. :doh:

[Speacy]

In editor, with -ARM missile type selected, the AI don't shoot AGM-88 on target (RADAR) and RTB, because of this we can't choose correctly the armament for this tgt type (auto mode use AGM-65 also )

 

Not fixed in 1.2.4.12547

 

AGM-88 is still not recognized as an ARM...

[marcoacv]

SU-25T missile KH-25mpu

 

The missile kh25mpu still with bad aim in version 1.2.4.12547. While the latest version 123 the operation was normal.

 

fresh install

Edited May 21, 2013 by marcoacv

[marcoacv]

Tunguska SA-19

 

SA19 Tunguska still firing missiles without any warning at rwr Russian aircraft.

 

1.2.4.12547

 

fresh install

Edited May 21, 2013 by marcoacv

[marcoacv]

DOG EAR RADAR "SBORKA"

 

The radar system "SBORKA" Dog Ear Radar remains silent in this version 124. In previous versions like the 123 that system was not silent. He sure emitted radiation. Now in version 124 I'm confused because I can see the antenna spinning but I get no signal radiation in my airplane.

 

1.2.4.12547

 

fresh install

Edited May 21, 2013 by marcoacv

[marcoacv]

SA-11 BUK

 

If the SA11 has four launchers and a radar antenna SR is correct I see the HUD with ELINT on only one diamond. But unfortunately I have to report that in the current version 124 and even with the new patch things are weird.

For I see in my hud four diamonds and the principal does not appear in this case the buk sr. I'm actually a little disappointed. I'm under the impression that the su25t is being left out.

 

1.2.4.12547

 

fresh install

Edited May 21, 2013 by marcoacv

[IvanK]

DCS 1.2.4.12547

 

SU27 RWR Signal strength bar still reversed, still moving anti clockwise with increasing signal strength.... Not fixed.

 

Edit graphic changed after Kukys post. ... disregard I am wrong anyway. All is actually ok.

Edited May 21, 2013 by IvanK

[Kuky]

IvanK, you write "should be anti clockwise" but arrow shows clockwise direction... I am confused

[159th_Viper]

DCS 1.2.4.12547

 

SU27 RWR Signal strength bar still reversed, still moving anti clockwise with increasing signal strength.... Not fixed.

 

 

It's correct - it must move anti-clockwise: Upside-down triangle is your ownship mark. Light strip signal strength runs anti-clockwise, terminating at your aircraft (ownship mark), ie further away, less lights lit - closer and more of the light-strip illuminated.

[IvanK]

IvanK, you write "should be anti clockwise" but arrow shows clockwise direction... I am confused

 

 

Yes I am confusing myself as well Kuky I am off on a tangent just re tested all is well :)

 

Yes thanks Viper I retract my erroneous bug report apologies for my brain fart :)

Edited May 21, 2013 by IvanK

[Ranger79]

If the SA11 has four launchers and a radar antenna SR is correct I see the HUD with ELINT on only one diamond. But unfortunately I have to report that in the current version 124 and even with the new patch things are weird.

For I see in my hud four diamonds and the principal does not appear in this case the buk sr. I'm actually a little disappointed. I'm under the impression that the su25t is being left out.

 

1.2.4.12547

 

fresh install

 

Same issue here AI SEAD are not going after the Dog Ear Radar even when attack unit is used.

[IvanK]

TWS 2 Label oddity ?

 

the MIG29 TWS target labelling seems weird to me. The Highest priority target (based on Range and closure) should logically be labelled T1.

 

In the images below we see 2 x A10 head on. The Left A10 is doing 300KMH and the right A10 is doing 500KMH. So the right hand A10 is the highest threat.

 

 

Before the Fire zone values are displayed both targets are visible on the MFD

 

As the 500KMH A10 comes inside Rmax It gets labelled T2 ??. When this happens the 300KMH A10 is dropped from the MFD ... I would have thought in TWS it would still be visible as no STT has occurred. The MFD presentation looks like the 500KMH is now under STT.

 

On firing T2 is engaged first (as its the highest threat) T2 then is engaged.

 

SUMMARY OF WHAT I THINK WOULD BE BETTER

Highest priority target should be labelled T1

T1 target should be the first missile.

T2 should be the other target and engaged with Missile 2

Both Targets should remain visible on the MFD even after the T labels

come up in the HUD.

[Kuky]

Thanks IvanK, I've just reported this T1 / T2 bug with MiG-29S TWS 2 mode... it seems left aircraft is always set as T1 and right aircraft as T2 so it means target priority is not how it's coded... but I agree it should be labeled as T1 for primary target and T2 as secondary.

[bueno]

yes there is a big problem with SEAD and AI.

 

AI are not efficient against sa10 with agm-88. most of time SA10 engage the sead and sead pack will jettison their missile to engage defensive move...stupid. Even if they fire the AGM, the missile is not able to destroy the radar of the SA10 group in one shoot !!!! Fix this please !!!

 

So the mission 5 and 6 of the F15 campaign are impossible to complete...very sad.