Print

Please login or register.
1 Hour 1 Day 1 Week 1 Month Forever
Login with username, password and session length

[trent]

It was probably the way I explained myself, sorry chaps, it is indeed the gun support frame Trent mentioned. When it swivels about the frame work gets in the view, so its not the gun itself, but the frame. I remembered many years ago, someone put out there a new GM4 with much thinner framework, but I am buggered if \I can remember where I saw/got it.

So, it was was the rotating framework holding the tail cone's glass that was bothering you on the G4M1, not the gun itself.

I have compiled two rear gunner options which I think might solve your problem, the first is a completely open tail cone that doesn't rotate. The second one (made by Ten010) is a frame that still rotates, but is much more open than the original G4M1 frame. You can try each one of them out and see which one you prefer. 

https://www.mediafire.com/download/g1y8r8siih09656/2x_G4M1_tail_gun_Options.7z


An aircraft I think you will also enjoy is Ten010's G4M2a (perhaps this is the Betty you were looking for). This aircraft features the more open rear gunner frame and Ten010 has also managed to keep the POV of the gunner looking through the gunsight, without altering the gun movement. Historically, the G4M2a had a number of improvements over the G4M1, such as an electrically powered dorsal turret, a search radar in the nose, 6,000km range thanks to larger fuel tanks as well as improved performance thanks to more powerful MK4T Kasei 25 engines ( 1,850 hp each ) and a laminar flow wing. You can get Ten010's G4M2a here...

https://www.sas1946.com/main/index.php/topic,30389.0.html

Regards

Trent

[Sun]

Hi,
 I am using 4.101 with UP3RC4 plus the 202 patch, I've noticed that Spitfires lastest models (1943 and after) they can fly unlimited time with wep-boost enabled without suffering any damage to the engine. There is no engine failure despite the long time flight and engine oveheat message.

Is this something that should be fixed somehow? Is this fixed in other versions of Il2 like 4.11, 4.12, etc?

Thanks.

[SAS~Storebror]

Hi Sun,

Thanks for the report.
The reason behind is IL-2's simple and unrealistic engine overheat code in combination with a set of questionable parameters for the Merlins of these late war Spits.
In IL-2, regardless which version, you can run an engine in overheat condition for as long as this has been specified in the engine model.
In case of the Merlin66 in UP3, this time is set to 280 seconds (4 minutes and 40 seconds).
Once your engine is in overheat condition, the time counted since overheating began is compared to that threshold and once it's been passed, engine damage will occur.
However in case of the late war spits, they're equipped with automatic radiators and the game will open up radiators in time, so that before the 280 seconds have passed, you will see a message "Engine: Normal" flicker for a split second.
That's when the overheat stops.
Unfortunately in IL-2's game code any stopped overheat will immediately reset the overheat timer.
This means you can run in overheat condition for 279 seconds, then cool down the engine so it's back "normal" for 1/10th of a second, then overheat it again for another 279 seconds and so on...

Overheat parameters differ much between different IL-2 versions and engine overheat has been changed from 4.10.1 to 4.11 (but mainly just in that high RPMs cause faster overheat, which was TD's way to fight all the upcoming modded jet planes), but the basic issue remains.

Two countermeasures apply:

• Change the engine's temperature settings to allow it to overheat at all.
• Change IL-2's overheat code completely to make it more realistic.
  This would require all engine models to be changed.

Best regards - Mike

[Sun]

Thanks Storebror.

I don't have any clue about the amount of time and work someone needs in order to apply the changes you mentioned. I only hope someone will start doing something about.

[macgiver]

Flying today with the Yak 7 (Patch Pack 302) I realized that the position of the wings is not correct, they are too far back:



to compare the same view with Patch Pack 301:



If anyone can verify it to know if it's a bug or not (maybe it's just my installation problem).
Thanks

[SAS~Storebror]

Yep, makes sense.
The Yak 7 pre PP 302 had serious issues with the center of gravity.
PP302 therefore put the 3D model back by app. 2 meters, but apparently I forgot to put back the cockpit location too.
Will be fixed in PP 303, thanks for the report.


Mike

[macgiver]

Thanks to you

[Phoenix]

changing the viewing angle does not work when enabled UP_animated_FOV_mod and when enable TrackIR
in BAT all work

[SAS~Storebror]

Negative. It works perfectly well. I'm using it myself all day like this.


Mike

[Phoenix]

my mistake
did not assign the correct buttons

I did not understand what was happening
restarted the IL-2 and changing the viewing angle does not work again

[SAS~Storebror]

my mistake
did not assign the correct buttons

In my cultural area this would suggest that it's working for you now, whereas this...

I did not understand what was happening
restarted the IL-2 and changing the viewing angle does not work again

...would suggest the opposite.
You got me confused now - is there anything left to help you with?


Mike

[Phoenix]

found the cause of the wrong behavior of UP_animated_FOV_mod
the problem appears only if in the Opentrack enable too large offset along the Z-axis

By the way, in BAT everything works fine.