4.10 Support & Bug Reporting

[Flanker35M]

S!

Well, for you guys complaining of the trim. Have you ever cared to look at the TRIM GAUGE in the Spitfire cockpit? I flew the Sissyfire and trimmed for fast cruise, the needle was less than half the range of the gauge and with less speed close to 0 position. And when had the trim at around 30% of the gauge reading the elevator was at roughly same position as in the photo above. I use trim on a slider, not tapping a key. Compare to FW190 that has the trim gauge too just aft of the throttle marked with an "alpha" sign. In Sissyfire the gauge is below the gear lamp indicator on left side.

[Ian Boys]

Hi Av,

OK, I tried your missions and they did work, so I saw how it should be. I tried mine again and it works fine for Red now (using IL-2 s2 as spotter) but I can't get it to work for blue with either Ju-87B2 or Hurri1 as spotters.

I reckon it might be something as daft as the order you put the things in the game, like with gliders.

Anyway, it's driving me nucking futs.

Can I send you my mission please? Might be something dead obvious ....

ian

[Aviar]

Originally Posted by Gryphon_

BUG: In an online game using a dedicated server with multiple targets for both sides to destroy, the game erroneously announces "RED WON" or "BLUE WON" when there are still many targets left to destroy.

I have never seen this announcement before in the online game, even though it is common in the offline game. It is very confusing as everyone stops playing, thinking one team has won, when they haven't. I have looked carefully at the target setup and can't see the problem. This has occured on more than one map. Here is the relevant section of the .mis file from one of them. This map announced 'RED WON' when Red had not won. If there is something I need to do differently in in the mis file, please advise. If not, this is a bug.

[Target]
1 0 0 0 500 126561 151887 500
1 0 0 0 500 67550 158981 500
1 0 0 0 500 108473 235433 500
1 0 0 0 500 71583 224151 500
1 0 0 0 500 68763 220959 500
1 0 0 0 500 78701 206214 500
1 0 0 0 500 83588 208925 500
1 0 0 0 500 72772 196655 500
1 0 0 0 500 95995 211405 500
1 0 0 0 500 85077 183711 500
1 0 0 0 500 90794 184815 500
1 0 0 0 500 87141 167354 500
1 0 0 0 500 96864 164910 500
1 0 0 0 500 102221 152155 500
1 0 0 0 500 106744 154120 500
1 0 0 0 500 62526 216413 500

If you post the entire mission, I will look at it for you. Otherwise, it's hard to evaluate.

Aviar

[Ian Boys]

Still having no luck with recon. And you can assign a Komet as recon but not a Fw-189. How is that?

[Artist]

Hi Folks,

first: Thank you so much!

Second: Are there DeviceLink set()-keys available for the new "Multi-throttle/prop support and radiator axis"?

I am using a G940 (ID 1, 2, and 3) plus Bodnar's BU0836A (ID 4) and I feed all of their axes to IL-2 through DeviceLink (the first because of the Reversal Bug, the last because IL-2 does not recognize the fourth device...)

oj123

[Aviar]

Originally Posted by Ian Boys

Still having no luck with recon. And you can assign a Komet as recon but not a Fw-189. How is that?

Sorry Ian, but I couldn't get your mission to work. It looks like a bug in MDS. It should be reported.

I could get the red recon working and the blue recon working, but not both at the same time. I tried a lot of combinations to try and trick it into working, but there is a bug in there somewhere.


**EDIT: I got it to work! I really don't like to fail so I went back to try something else. Try adding both the red and blue recon planes in BOTH recon lists. This worked for me. This is still an MDS bug and should be reported to Zuti/DT. However, this may be a good workaround for now.


Aviar

[vparez]

Originally Posted by Flanker35M

S!

Well, for you guys complaining of the trim. Have you ever cared to look at the TRIM GAUGE in the Spitfire cockpit? I flew the Sissyfire and trimmed for fast cruise, the needle was less than half the range of the gauge and with less speed close to 0 position. And when had the trim at around 30% of the gauge reading the elevator was at roughly same position as in the photo above. I use trim on a slider, not tapping a key. Compare to FW190 that has the trim gauge too just aft of the throttle marked with an "alpha" sign. In Sissyfire the gauge is below the gear lamp indicator on left side.

I don't know what are you implying by your post, but the comparison with FW shows that for a trimmed flight at 100% throttle, FW shows very small displacement of the needle, and it surely needs much less trim than the Spitfire.

I don't know who is a vintage plane pilot here, but as far as I know, a plane never needs much trim for a cruise flight. If you need to trim your plane so much for a cruise flight, it is a very bad design. People can hate the Spitfire here as much as they want, but it was a very well designed airplane, which is confirmed if nothing else then just by its longevity in service.

I don't think that TD should base the FM of a spit on a few photos of in-flight spitfire; and that doesn't explain the fact that it rolls like crazy all the time to the right.

Still no comment from TD on this. I would say they compiled 4.10 with a wrong version of the FM, that's all.

[IvanK]

...."I don't think that TD should base the FM of a spit on a few photos of in-flight spitfire..."

They don't, the images were provided as a response to this thread to indicate typical Spitfire Elevator position in a trimmed 1G cruise state. There are plenty of other images around of Spits in the Luft showing this elevator deflection.

No Rollnloop .. I should be so lucky . The Spitfire pilot is a friend who provided me with the images from a photoshoot.

[Ian Boys]

Thanks gabe!

[bolox]

Originally Posted by vparez

I don't know what are you implying by your post, but the comparison with FW shows that for a trimmed flight at 100% throttle, FW shows very small displacement of the needle, and it surely needs much less trim than the Spitfire.

if you test the fw you will see that full elev trim in either direction only moves the gauge to~1/2 the scale deflection whereas spits move to full scale deflection, so there is much less movement to see. it has been that way for as long as i can remember.

as a side note to this- how many people use the recomended setting for takeoff trim of ~1 div nose down trim for take off in spits?(from pilot's notes MKV)