Tobruk issues

[Cinder]

Hi,

 

I had Blitz working well, and just tried Tobruk.   A couple of issues issues I'm running into with the Tobruk patch:

1)  Black screen after clicking "Fly".   Wait a while, nothing.   Alt-tab out (set to Fullscreen if it makes a difference), hear a "click" and go back into game where it launches.   Will hang at black screen until I do this process...

2) Realism setting in Blitz allowed me to "F2" or "F3" external views.   However, it's behaving intermittently in Tobruk.  It does not consistently switch views when F1, F2 or F3 are pushed; for instance once i switched view to F3, I was locked into that view and wouldn't register F1 to return to cockpit.  Left to Controls menu and back in - still locked.  Exited program and restarted - it behaved same way.  Likewise, I couldn't switch consistently to F2 (or back to F1), but could go to F3...    No changes were made to controls from my setup in Blitz, and my keyboard outside of game is working like a champ.   Double checked Control mapping, and they are set correctly for F1 to cockpit, etc.

3) Customize plane section, plane graphic doesn't want to respond to moving the model to different angles (at least not consistently)

4) Steam indicates Blitz continues to run long after you have exited game.  Trying to "stop" game via Steam option doesn't work.   When you try to shut down Steam it hangs up due to Blitz not shutting down properly.  Process is not "obvious" in task manager.   When I restarted Steam, it indicated Blitz/Tobruk was still running.  This happened multiple times (shut off PC, relaunched Blitz, exited out, but Steam seeing it running in background.

 

System specs if it matters:

3700X

32GB RAM

GTX 1080

graphics set to 1440, 144hz

Game installed on SSD

Windows 10 current updates

Current NVidia drivers (451.67)

Game initiated via Steam launch, same as I doing with Blitz

No background apps running aside from browser, Acrobat reader, Steam, TrackIR

 

Edited August 7, 2020 by Cinder

[Buzzsaw]

Hello Cinder

 

Sounds to me like there may be something corrupted in your install.

 

I would recommend you first of all delete the cache file from Documents/1C SoftClub/il-2 sturmovik cliffs of dover/  (always delete this file when adding a new module)

 

Then I would suggest verifying your game install in Steam.

 

If that doesn't work:

 

-  Make sure the Steam overlay is turned off.

 

-  Check to see if your copy of Microsoft Net Framework is the latest version.

 

-  Check to see what other programs are running when you launch the game.

[Panezz]

6 hours ago, Cinder said:

Hi,

 

I had Blitz working well, and just tried Tobruk.   A couple of issues issues I'm running into with the Tobruk patch:

1)  Black screen after clicking "Fly".   Wait a while, nothing.   Alt-tab out (set to Fullscreen if it makes a difference), hear a "click" and go back into game where it launches.   Will hang at black screen until I do this process...

Same problem for me

 

 

Same problem for me

[Cinder]

9 hours ago, Buzzsaw said:

Hello Cinder

 

Sounds to me like there may be something corrupted in your install.

 

I would recommend you first of all delete the cache file from Documents/1C SoftClub/il-2 sturmovik cliffs of dover/  (always delete this file when adding a new module)

 

 

Hi Buzzsaw,

 

Thanks for your quick response and help, and the cache delete seemed to do the trick for the issues I was experiencing.   Would be great it that was an automated step during patching.

 

 

[Dirtbag_Jim]

Hi @Buzzsaw,

 

I've noticed there Kittyhawk Mk Ia Trop seems to have an oil overheating issue, the manual says to keep the oil temps below 85C, but even with max radiator and running on cruise settings the oil temp fails to go below 88C and the engine eventually overheats and fails.

 

Hoping this could be fixed like how the overheating problem for the Trop versions of the Spitfire and Hurricane were resolved so quickly.

 

Cheers for any help you could provide!

[Grancesc]

13 hours ago, Cinder said:

Hi,

 

I had Blitz working well, and just tried Tobruk.   A couple of issues issues I'm running into with the Tobruk patch:

1)  Black screen after clicking "Fly".   Wait a while, nothing.   Alt-tab out (set to Fullscreen if it makes a difference), hear a "click" and go back into game where it launches.   Will hang at black screen until I do this process...

 

 

Exactly the same malfunction occurs for me.  I tried all your suggestions to no avail:

- Steam overlay is turned off.

- Other 3rd party programs disabled in the back ground.

- Re-installed (3 times) with turn off anti-virus.

- Have latest Windows update and .NET Framework

- Deleted cache in 1C SoftClub directory

- Did verify  game install in Steam.

 

My installation works without any problems for the simulations IL-2 Great Battles and DCS. You seem to have a serious problem here. Please fix it.

[BB5000]

Have you tried to run in ”Pseudo” mode i Video settings ?

[Buzzsaw]

5 hours ago, Dirtbag_Jim said:

Hi @Buzzsaw,

 

I've noticed there Kittyhawk Mk Ia Trop seems to have an oil overheating issue, the manual says to keep the oil temps below 85C, but even with max radiator and running on cruise settings the oil temp fails to go below 88C and the engine eventually overheats and fails.

 

Hoping this could be fixed like how the overheating problem for the Trop versions of the Spitfire and Hurricane were resolved so quickly.

 

Cheers for any help you could provide!

Hello DirtbagJim

 

What throttle and rpm are you running when you get the overheat?

 

If you run 100% throttle and 3000 rpm all the time, yes, you will see an overheat.

 

Your 30 minute climb settings are 42 in (boost) and 2800 rpm.  These will allow you to run generally as long as you want.

 

Full throttle (56 in) and 3000 rpm is only scheduled for 5 minutes... but again, that depends on your speed.  At very slow speeds you will see overheat faster.  At very high speeds, you may be able to run those power settings much longer.  Depends on the volume and speed of the flow of air through the radiators.

[Dirtbag_Jim]

1 hour ago, Buzzsaw said:

Hello DirtbagJim

 

What throttle and rpm are you running when you get the overheat?

 

If you run 100% throttle and 3000 rpm all the time, yes, you will see an overheat.

 

Your 30 minute climb settings are 42 in (boost) and 2800 rpm.  These will allow you to run generally as long as you want.

 

Full throttle (56 in) and 3000 rpm is only scheduled for 5 minutes... but again, that depends on your speed.  At very slow speeds you will see overheat faster.  At very high speeds, you may be able to run those power settings much longer.  Depends on the volume and speed of the flow of air through the radiators.

 

Thanks for such a prompt response!

 

Sorry for forgetting to put my RPM and Boost settings in my initial post. I've been running the plane with 100% radiator, at the recommended cruise settings (37" Boost and 2600 RPM) and can't seem to get the engine oil temps below 88 degrees (87 degrees at best when in a dive), while the manual says to keep engine oil temp below 85 degrees so the plane seems to already be overheating on just cruise settings. As soon as I run the plane at the high speed setting stated in the flashcard (42" Boost, 3000 RPM), the engine oil temp very quickly goes over 90 degrees, and eventually the engine dies from overheating (usually says engine governor failure) within less than 5 mins.

 

This is for the Kittyhawk Mk Ia Trop on the Tobruk Map, using a Quick Mission with air spawn.

 

EDIT: On a side note I'm very happy with TFS 5.0 and all the new content, as well as all the little tweaks and fixes, it's brought. The new sound system is especially amazing too. Already know that it's turned CLoD into my new favorite sim and I hope the development team knows how appreciated all the work that went into it is.

 

Edited August 7, 2020 by Dirtbag_Jim
added a note

[Buzzsaw]

15 minutes ago, Dirtbag_Jim said:

 

Thanks for such a prompt response!

 

Sorry for forgetting to put my RPM and Boost settings in my initial post. I've been running the plane with 100% radiator, at the recommended cruise settings (37" Boost and 2600 RPM) and can't seem to get the engine oil temps below 88 degrees (87 degrees at best when in a dive), while the manual says to keep engine oil temp below 85 degrees so the plane seems to already be overheating on just cruise settings. As soon as I run the plane at the high speed setting stated in the flashcard (42" Boost, 3000 RPM), the engine oil temp very quickly goes over 90 degrees, and eventually the engine dies from overheating (usually says engine governor failure) within less than 5 mins.

 

This is for the Kittyhawk Mk Ia Trop on the Tobruk Map, using a Quick Mission with air spawn.

 

EDIT: On a side note I'm very happy with TFS 5.0 and all the new content, as well as all the little tweaks and fixes, it's brought. The new sound system is especially amazing too. Already know that it's turned CLoD into my new favorite sim and I hope the development team knows how appreciated all the work that went into it is.

 

Ok, you are reading from the old flashcard manuals which are not accurate... these were included mistakenly.

 

The new flashcard manuals are available for download in the Update section of these forums.

 

The max temp for the Kittyhawk is actually 95 degrees C... not 85.

 

Max. temps for the rads is 125 C.

 

You can run 2800 rpm and 42 inches boost without a problem for 30 minutes... should be able to use 75% radiator or maybe 50% at low alts.

 

Higher boost and rpms are limited... max 5 minutes, less if you are turning at low speeds.

 

We will look at the overheat for the Kittyhawk again.

[Dirtbag_Jim]

1 minute ago, Buzzsaw said:

Ok, you are reading from the old flashcard manuals which are not accurate... these were included mistakenly.

 

The new flashcard manuals are available for download in the Update section of these forums.

 

The max temp for the Kittyhawk is actually 95 degrees C... not 85.

 

Max. temps for the rads is 125 C.

 

You can run 2800 rpm and 42 inches boost without a problem for 30 minutes... should be able to use 75% manual or maybe 50% at low alts.

 

Thanks again for such a quick response, haha was literally just editing my previous comment to say your advice worked great and solved my problem!

 

At 42" Boost and 2800RPM I have no issues with the oil temp going over 90 (and eventually beyond and seizing up). Thanks again for your help, really much appreciated! o7

[Buzzsaw]

13 minutes ago, Dirtbag_Jim said:

 

Thanks again for such a quick response, haha was literally just editing my previous comment to say your advice worked great and solved my problem!

 

At 42" Boost and 2800RPM I have no issues with the oil temp going over 90 (and eventually beyond and seizing up). Thanks again for your help, really much appreciated! o7

We will look at the Kittyhawk overheat again and see if the overheat modeling is a little harsh.

Oh, by the way, normal combat fuel load is 79% for the Kittyhawk... don't load the behind the seat tank... that was for longer range missions.

 

At 79% the Kittyhawk is carrying more fuel than a Spit at 100%.

 

The loadout weight shows black when the aircraft is at normal combat load, red when overloaded.

[Dirtbag_Jim]

7 minutes ago, Buzzsaw said:

We will look at the Kittyhawk overheat again and see if the overheat modeling is a little harsh.

 

I really respect and appreciate how dedicated you and the team are to addressing player concerns

 

I'm sure you're very busy with other things, so I wouldn't worry too much about the Kittyhawk overheating. Seems like it was just a combination of me running on poor engine settings, and me mistakenly thinking the plane was overheating on cruise, which I thought was something the team would want to know (both just issues stemming from incorrect information I got in the old manual, which has thankfully been rectified with the updated manuals).

 

Apologies for any inconvenience/hassle I may have caused!

[Buzzsaw]

6 minutes ago, Dirtbag_Jim said:

 

I really respect and appreciate how dedicated you and the team are to addressing player concerns

 

I'm sure you're very busy with other things, so I wouldn't worry too much about the Kittyhawk overheating. Seems like it was just a combination of me running on poor engine settings, and me mistakenly thinking the plane was overheating on cruise, which I thought was something the team would want to know (both just issues stemming from incorrect information I got in the old manual, which has thankfully been rectified with the updated manuals).

 

Apologies for any inconvenience/hassle I may have caused!

Happy to answer your questions!  ?

[Art-J]

Buzz, any chance of modyfying flashcards in the future to have Beaufighter engine settings given in RPM and lbs of boost rather than percentages? The latter don't tell me anything - I play without info window, relying strictly on instruments and I'm sure I'm not the only one. While we're at it, some planes have a mix of percentages and RPMs, some have pressure units and RPMs - It's all a bit messy.

 

I'd suggest sticking to one convention, or writing both percentages and actual units (there seems to be enough room in each table cell for that) so that each player can check the data he's used to.

Edited August 7, 2020 by Art-J

[Buzzsaw]

1 hour ago, Art-J said:

Buzz, any chance of modyfying flashcards in the future to have Beaufighter engine settings given in RPM and lbs of boost rather than percentages? The latter don't tell me anything - I play without info window, relying strictly on instruments and I'm sure I'm not the only one. While we're at it, some planes have a mix of percentages and RPMs, some have pressure units and RPMs - It's all a bit messy.

 

I'd suggest sticking to one convention, or writing both percentages and actual units (there seems to be enough room in each table cell for that) so that each player can check the data he's used to.

The Beaufighter has been changed to boost and rpm in the updated versions... please check the downloads available in the Update section of this forum.  ?

[Art-J]

Thank you very much. Someone pointed me to an allegedly updated version yesterday, but it must've been still a bit older revision. Just got the latest ones, I'm good.

[=GW=501Railgun]

I also have the same problem. 3800x+2080ti loads the aircraft and loading，it is very stuck , while the other computer, 1060+i5, is particularly smooth. I guess it is caused by the blitzkrieg’s support for AMD’s CPU.

[Dirtbag_Jim]

Hey @Buzzsaw,

 

I've noticed a view problem related to the Tomahawk MK II Trop Late (possibly the early version as well, haven't double checked).

 

You're unable to turn fully behind (180 degrees backwards), which you're able to do in all other fighters, and it seems to have a roughly 90 degree gap where you're unable to turn directly to the rear. (As shown in the diagram below, where the red is the area you're unable to turn).

It makes it impossible to get a direct view of high six (most common area to get bounced from) without having a very zoomed out FOV to have your rear in the periphery of your vision. However as soon as you need to zoom in to identify whats on your tail, the zoomed in FOV no longer has the direct six in view anymore (As shown in the diagram below, with yellow showing FOV).

 

The lack of ability to turn a complete 360 (or direct 180 to the rear) in the Tomahawk is a huge handicap, and seems to be an issue present only on the Tomahawk. Hopefully this issue isn't too difficult to fix and can be fixed in the upcoming patch to bring it in line with all the rest of the planes in the game (which all have the ability to turn a full 360 degrees in-cockpit).

 

Any help you could provide would be greatly appreciated!

 

 

 

 

[dazako]

11 hours ago, Dirtbag_Jim said:

Hey @Buzzsaw,

 

I've noticed a view problem related to the Tomahawk MK II Trop Late (possibly the early version as well, haven't double checked).

 

You're unable to turn fully behind (180 degrees backwards), which you're able to do in all other fighters, and it seems to have a roughly 90 degree gap where you're unable to turn directly to the rear. (As shown in the diagram below, where the red is the area you're unable to turn).

It makes it impossible to get a direct view of high six (most common area to get bounced from) without having a very zoomed out FOV to have your rear in the periphery of your vision. However as soon as you need to zoom in to identify whats on your tail, the zoomed in FOV no longer has the direct six in view anymore (As shown in the diagram below, with yellow showing FOV).

 

The lack of ability to turn a complete 360 (or direct 180 to the rear) in the Tomahawk is a huge handicap, and seems to be an issue present only on the Tomahawk. Hopefully this issue isn't too difficult to fix and can be fixed in the upcoming patch to bring it in line with all the rest of the planes in the game (which all have the ability to turn a full 360 degrees in-cockpit).

 

Any help you could provide would be greatly appreciated!

 

 

 

 

 

Actually there are several planes off the top of my head from stock Cliffs to new additions with limited head-turn range, while others are full radii 'Linda Blair'. Always been a bit of an annoyance so far as flying using visual reference, and the sudden stop gives the impression trackir has lost contact, which is distracting. I assume these are limitations set in the 3D model ? The Blenheim for eg has controls in positions that can't be viewed and restricted rotation in all 3 crew positions. I've not experienced VR but assume there's no such limits in any direction ? All technical stuff beyond my comprehension of course. 

Not to detract from the amazing work that has been done to date.

Cheers

Daz

Edited August 10, 2020 by dazako

[Dirtbag_Jim]

5 hours ago, dazako said:

 

Actually there are several planes off the top of my head from stock Cliffs to new additions with limited head-turn range, while others are full radii 'Linda Blair'. Always been a bit of an annoyance so far as flying using visual reference, and the sudden stop gives the impression trackir has lost contact, which is distracting. I assume these are limitations set in the 3D model ? The Blenheim for eg has controls in positions that can't be viewed and restricted rotation in all 3 crew positions. I've not experienced VR but assume there's no such limits in any direction ? All technical stuff beyond my comprehension of course. 

Not to detract from the amazing work that has been done to date.

Cheers

Daz

 

That's interesting! I hadn't realized there were other aircraft with the limited head-turn range (like the Blenheim), but then again I've only flown fighters so far in CLoD. Good reminder for me to start branching out. What were some of the other planes without the ability to go full Linda Blair (haha loved that) that you know of?

Hopefully the head-turn thing is something that can be fixed and isn't a 3D model problem and just an understandably small oversight (considering the scale of the sim and the amount of work that goes into it).

 

Cheers