Fulqrum Publishing Home   |   Register   |   Today Posts   |   Members   |   UserCP   |   Calendar   |   Search   |   FAQ

Go Back   Official Fulqrum Publishing forum > Fulqrum Publishing > IL-2 Sturmovik > Daidalos Team discussions

Reply
 
Thread Tools Display Modes
  #1  
Old 04-28-2012, 03:53 PM
Fall_Pink? Fall_Pink? is offline
Approved Member
 
Join Date: Oct 2007
Location: Netherlands
Posts: 100
Default

4.11.1 AI / Jet bug:

Jets like He162 and Me262 can't take off anymore. They overheat when they're half way the runway and have diffculties gaining altitude. They fail to climb and/or their engines catch fire. Tested with he162 and single mission 'rapid strike mission'. With the rapid strike mission, the first he162 cannot gain sufficient alititude and crashes into the woods at the end of the runway.

edit: small correction. Bug is also present in 4.11 + hotfix. Base closure with YP80 catches fire when taking off and 'rapid strike' mission produces the same result. I.e. he162 is unabnle to take off and it's engine starts to burn.

Rgs,
Mark
__________________
Intel Core i7 2600 @ default clocks
MSI P67A-GD65A Motherboard
Vertex2 SSD
Raid1 1 Tb data disk
8GB DDR3-1600
MSI Geforce 680GTX @ default clocks
Hotas Cougar
X-Fi Music

Last edited by Fall_Pink?; 04-28-2012 at 04:33 PM.
Reply With Quote
  #2  
Old 04-28-2012, 09:21 PM
Luno13 Luno13 is offline
Approved Member
 
Join Date: Oct 2011
Posts: 370
Default

I just made tests and I have no issues with the jets. Make sure to increase power slowly. Too fast and the engine will catch fire.

Also, I tend not to add more than 80% power, to avoid overheating.

Acceleration is slow, and jerking the plane off the runway won't help. I pull back on the stick just enough to raise the nose. The plane will roll on the main wheels until it's "ready" to fly, and will lift off on its own at the right speed. Raise gear immediately, lower the nose to accelerate and raise flaps in increments.
Reply With Quote
  #3  
Old 04-28-2012, 09:26 PM
Fall_Pink? Fall_Pink? is offline
Approved Member
 
Join Date: Oct 2007
Location: Netherlands
Posts: 100
Default

Quote:
Originally Posted by Luno13 View Post
I just made tests and I have no issues with the jets. Make sure to increase power slowly. Too fast and the engine will catch fire.

Also, I tend not to add more than 80% power, to avoid overheating.

Acceleration is slow, and jerking the plane off the runway won't help. I pull back on the stick just enough to raise the nose. The plane will roll on the main wheels until it's "ready" to fly, and will lift off on its own at the right speed. Raise gear immediately, lower the nose to accelerate and raise flaps in increments.
Luno13,

Manually there will be no problem with any jet I guess and I think it's the auto pilot that messes it up some how.

I tested the he162 'rapid strike mission' with auto pilot enabled for take off. I checked a couple of times and nearly all of them crash into the hillside.

Please check if you get the same behavior with this mission.

Rgs,
Mark
__________________
Intel Core i7 2600 @ default clocks
MSI P67A-GD65A Motherboard
Vertex2 SSD
Raid1 1 Tb data disk
8GB DDR3-1600
MSI Geforce 680GTX @ default clocks
Hotas Cougar
X-Fi Music
Reply With Quote
  #4  
Old 04-28-2012, 11:32 PM
JtD JtD is offline
Il-2 enthusiast & Moderator
 
Join Date: Oct 2007
Posts: 903
Default

The Heinkels indeed crash, but it already happened in 4.09. Do you know the last version it worked with? Overheat in 4.11 came too quick for some jets, but this was corrected in 4.11.1 and should no longer be an issue. I haven't seen one catching fire on take off, yet.
Reply With Quote
  #5  
Old 04-29-2012, 09:43 AM
Fall_Pink? Fall_Pink? is offline
Approved Member
 
Join Date: Oct 2007
Location: Netherlands
Posts: 100
Default

Quote:
Originally Posted by JtD View Post
The Heinkels indeed crash, but it already happened in 4.09. Do you know the last version it worked with? Overheat in 4.11 came too quick for some jets, but this was corrected in 4.11.1 and should no longer be an issue. I haven't seen one catching fire on take off, yet.
I did not test it with 4.09, so I can't confirm that.

I tried the misison on 4.11 + hotfix and 4.11.1 only. With both versions they crash into the hillside. I'm not sure if overheating has been fixed for jets yet when auto pilot is in control. The overheating warning appears too early I guess.

To check overheating and autopilot behavior, I did some other tests with other fighters as well (Do335-v13 and La7 from single mission section all with AP enabled) and they never seem to overheat. Not during take off and not while they fly their waypoints. In this mission La7 never overheats, and if it does then only during engaging enemy fighters and for a very short duration.

With the Do335 mission, it reached 550 IAS all along it's waypoints and an overheating warning message never appeared.

I can't assess if this is 'real' or not. I just find it weird that some planes, when flown by AP do not have any overheating issues, while some others have them so quickly.

Rgs,
Mark
__________________
Intel Core i7 2600 @ default clocks
MSI P67A-GD65A Motherboard
Vertex2 SSD
Raid1 1 Tb data disk
8GB DDR3-1600
MSI Geforce 680GTX @ default clocks
Hotas Cougar
X-Fi Music
Reply With Quote
  #6  
Old 04-29-2012, 01:41 AM
Aviar's Avatar
Aviar Aviar is offline
Approved Member
 
Join Date: Dec 2007
Location: New Jersey, USA
Posts: 545
Default

Quote:
Originally Posted by Fall_Pink? View Post
4.11.1 AI / Jet bug:

Jets like He162 and Me262 can't take off anymore. They overheat when they're half way the runway and have diffculties gaining altitude. They fail to climb and/or their engines catch fire. Tested with he162 and single mission 'rapid strike mission'. With the rapid strike mission, the first he162 cannot gain sufficient alititude and crashes into the woods at the end of the runway.

edit: small correction. Bug is also present in 4.11 + hotfix. Base closure with YP80 catches fire when taking off and 'rapid strike' mission produces the same result. I.e. he162 is unabnle to take off and it's engine starts to burn.

Rgs,
Mark
There is no bug here. The jet AI takes off perfectly fine in 4.11.1. Even the Player's plane (in offline missions) will take off correctly if the Autopilot is used. I'm not sure what your problem may be.

I tested the Rapid Strike mission and the jet AI all take off just fine. However, they do crash into the hill. This may be due to new FM's.

I tried a quick workaround and it worked. Just open the mission in the FMB and give all the 262 and 162 flights 65% fuel instead of 100%. This makes them lighter and they don't crash anymore.

Aviar
__________________
Intel i7-4790 4-Core @3.60GHz
Asus Z97-C Motherboard
16GB DDR-3 1600 SDRAM @800 MHz
NVIDIA GTX 760 - 2GB
Creative SB ZX SBX
Logitech X-530 5.1 Speakers
27" AOC LED - 2752
Logitech G15 Gaming Keyboard
CH FighterStick-Pro Throttle-Pro Pedals
Logitech G13 Gameboard
GoFlight GF-T8 Module
WIN 8.1
Reply With Quote
  #7  
Old 04-29-2012, 09:57 AM
Fall_Pink? Fall_Pink? is offline
Approved Member
 
Join Date: Oct 2007
Location: Netherlands
Posts: 100
Default

Quote:
Originally Posted by Aviar View Post
There is no bug here. The jet AI takes off perfectly fine in 4.11.1. Even the Player's plane (in offline missions) will take off correctly if the Autopilot is used. I'm not sure what your problem may be.

I tested the Rapid Strike mission and the jet AI all take off just fine. However, they do crash into the hill. This may be due to new FM's.

I tried a quick workaround and it worked. Just open the mission in the FMB and give all the 262 and 162 flights 65% fuel instead of 100%. This makes them lighter and they don't crash anymore.

Aviar
Aviar,

It looks like these new patches thus created some incompatabilities with older missions which need fixing. Either by changing the missions or having another look at the overheating and AP engine management part.

Is it realistic a He162 overheats when it's only halfway the runway on take off?

I'm not aware of any new FM's for these planes. Did 4.11.1 introduce a new fm for these types?

Rgs,
Mark
__________________
Intel Core i7 2600 @ default clocks
MSI P67A-GD65A Motherboard
Vertex2 SSD
Raid1 1 Tb data disk
8GB DDR3-1600
MSI Geforce 680GTX @ default clocks
Hotas Cougar
X-Fi Music
Reply With Quote
  #8  
Old 04-29-2012, 11:47 AM
JtD JtD is offline
Il-2 enthusiast & Moderator
 
Join Date: Oct 2007
Posts: 903
Default

Bug's been present at least since 4.09.
FM's haven't been changed for the He 162 for ages.
Overheat in 4.11 didn't work well with AI for some jets.
Overheat in 4.11.1 works with AI in all jets.
Jet engines overheat differently than piston engines, both in real life and in game.

To sum it up, either the He 162 FM needs to be fixed in which case real life data on low speed acceleration, handling and take off distance would come in handy, or very simple, the mission needs to be adjusted.

Unless you want to research He 162 performance, don't spend sleepless nights over the issue.
Reply With Quote
  #9  
Old 04-29-2012, 11:49 AM
Ace1staller Ace1staller is offline
Approved Member
 
Join Date: Apr 2011
Location: somewhere in the united states
Posts: 125
Default

I have a problem with the Quick mission builder. It gives me a blank screen when ever I click the button however this was before the release of 4.11.1 and I'll soon post a picture to show my problem.
Reply With Quote
  #10  
Old 04-29-2012, 11:51 AM
JtD JtD is offline
Il-2 enthusiast & Moderator
 
Join Date: Oct 2007
Posts: 903
Default

Have you tried deleting the .last.quick file from the Quicks folder in your il-2 installation?
Reply With Quote
Reply

Thread Tools
Display Modes

Posting Rules
You may not post new threads
You may not post replies
You may not post attachments
You may not edit your posts

BB code is On
Smilies are On
[IMG] code is On
HTML code is Off

Forum Jump


All times are GMT. The time now is 05:29 AM.


Powered by vBulletin® Version 3.8.4
Copyright ©2000 - 2025, Jelsoft Enterprises Ltd.
Copyright © 2007 Fulqrum Publishing. All rights reserved.