Cliffs of Dover Desert Wings Tobruk - Bug Report Thread

[Plurp]

10 minutes ago, Stache999 said:

For me - E7 and E4 Trop - cannot open canopy/door - cannot bail out.
I tried a 110 Trop and the canopy and bailout works okay for it.

Use the canopy jettison key binding under the general category in the key bindings.  "Jettison canopy/hatch/door".  Then the bail out key.

Edited August 10, 2020 by Plurp

[56RAF_Stickz]

Wellington 1c, flown 3 times now. Have only tried the 1c, but both trop in Tobruk and non trop version in BoB map. I use the bomb door toggle control (not the individual up/down selection). On ground prior to take off the toggle works fine. First press opens bomb door, second closes them. However, it appears that once I enter the bomb aimer position and leave it to return back to cockpit, selecting bomb door opens and immediately closes them. The only way to get them to stay open is via the cockpit lever (not a big deal but when it gets busy near target its harder to remember this). Similar case to close them.
This happens whether taken off or when still on ground, engines on or off. So once entered the position to set the bomb sight prior to take off and then return to cockpit, the bomb door toggle doesnt work properly any more.

[I/JG54_chuishan]

51 minutes ago, 56RAF_Stickz said:

Wellington 1c, flown 3 times now. Have only tried the 1c, but both trop in Tobruk and non trop version in BoB map. I use the bomb door toggle control (not the individual up/down selection). On ground prior to take off the toggle works fine. First press opens bomb door, second closes them. However, it appears that once I enter the bomb aimer position and leave it to return back to cockpit, selecting bomb door opens and immediately closes them. The only way to get them to stay open is via the cockpit lever (not a big deal but when it gets busy near target its harder to remember this). Similar case to close them.
This happens whether taken off or when still on ground, engines on or off. So once entered the position to set the bomb sight prior to take off and then return to cockpit, the bomb door toggle doesnt work properly any more.

 

I believe it's an old bug, since He.111 back in the day behaves the same regarding bomb bay door control.

 

Using seperate keys to open/close the bomb bay will be fine. I personally use backspace and '\' key for this job.

[dazako]

1 hour ago, 56RAF_Stickz said:

Wellington 1c, flown 3 times now. Have only tried the 1c, but both trop in Tobruk and non trop version in BoB map. I use the bomb door toggle control (not the individual up/down selection). On ground prior to take off the toggle works fine. First press opens bomb door, second closes them. However, it appears that once I enter the bomb aimer position and leave it to return back to cockpit, selecting bomb door opens and immediately closes them. The only way to get them to stay open is via the cockpit lever (not a big deal but when it gets busy near target its harder to remember this). Similar case to close them.
This happens whether taken off or when still on ground, engines on or off. So once entered the position to set the bomb sight prior to take off and then return to cockpit, the bomb door toggle doesnt work properly any more.

 

I never knew about this one. I'd tried the 'bomb bay doors toggle' to use 1 button instead of 2 and found the same issue. If you Alt F2 from bomb aimer to cockpit, or go to another position other than cockpit, then the toggle functions as normal again. 

 

Daz

Edited August 11, 2020 by dazako

[Barnacles]

Here's a shot trying to look behind be in a Tomahawk.

The canopy is open but because the head movement is so restricted this is the best I can do.

Is it possible to let the head be moved over to one side and rotated a bit more?

 

In fact the area in which you can move your head is less restricted if the canopy is closed!

Has there been a mix up in the modelling?

 

 

 

•  
• Quote
•  
• Edit
•  
• Options  

[56RAF_Stickz]

8 hours ago, I/JG54_chuishan said:

 

I believe it's an old bug, since He.111 back in the day behaves the same regarding bomb bay door control.

 

Using seperate keys to open/close the bomb bay will be fine. I personally use backspace and '\' key for this job.

didnt realise that. but then its quite some time since I flew German bombers in CloD. Do not remember noticing it then (perhaps the control is in bomb aimer position? there), and of course blennie does it for you. As for separate keys, a) try very hard to keep all flight sims using same keys/HOTAS controls for same functions (brain too old to flip around) and (b) I dont have enough HOTAS keys free anyway to use open and shut. Even getting supercharger up/down was hard as opposed to il2 single step next.

8 hours ago, dazako said:

If you Alt F2 from bomb aimer to cockpit, or go to another position other than cockpit, then the toggle functions as normal again. 

ha ha yes, and of course I removed the alt F2 cos had no idea what it was for and in blitz appeared to be a double of external views. Only just found out about its use.

[ITAF_Airone1989]

3 hours ago, 71st_AH_Barnacles said:

Here's a shot trying to look behind be in a Tomahawk.

The canopy is open but because the head movement is so restricted this is the best I can do.

Is it possible to let the head be moved over to one side and rotated a bit more?

 

In fact the area in which you can move your head is less restricted if the canopy is closed!

Has there been a mix up in the modelling?

 

 

 

•  
•  
• Quote
•  
• Edit
•  
• Options  

It could be the air flow: when canopy is open the air flow is so strong that you cannot keep your head out from the frontal glass... That's why is stuck in the center

[LLv34_Flanker]

S!

 

Managed to fix my sound issues per Buzzaw´s tip. Turned the game sounds to 100% and then with Windows Sound Mixer adjusted the output levels of Tobruk to be tolerable.

[Barnacles]

Right, I think I've worked out why CloD feels ultra weird to me. It seems there's a slight delay between my control inputs and when they're reflected in game. Like there's some lag or something. It's very slight but I really can't aim for S&%$. Is this 'just how it is' or is there something amiss?

[ITAF_Airone1989]

16 minutes ago, 71st_AH_Barnacles said:

Right, I think I've worked out why CloD feels ultra weird to me. It seems there's a slight delay between my control inputs and when they're reflected in game. Like there's some lag or something. It's very slight but I really can't aim for S&%$. Is this 'just how it is' or is there something amiss?

 

Instead of use the stick, try to adjust the airplane's trim.

I found out that when it's correctly trimmed hit somebody it's not so difficult, otherwise it's a real challenge

[Barnacles]

7 minutes ago, ITAF_Airone1989 said:

 

Instead of use the stick, try to adjust the airplane's trim.

I found out that when it's correctly trimmed hit somebody it's not so difficult, otherwise it's a real challenge

That's not going to help, but thank you anyway.

Edited August 11, 2020 by 71st_AH_Barnacles

[ITAF_Airone1989]

3 minutes ago, 71st_AH_Barnacles said:

That's not going to help.

 

Did you check if you have some death zone in the axis control settings?

[Barnacles]

Just now, ITAF_Airone1989 said:

 

Did you check if you have some death zone in the axis control settings?

Yeah, I've got no dead zone, I've tried all the different sensitivities. Do you have a lag?

 

[Yardstick]

I don't know if it just a delay in the cannon sounds on the 109s or they just have a slow response but there appears to be a c. 0.5 sec delay between pressing the trigger for the cannon (s) and them firing.  I've had to adjust my timing of snap shots to reflect this as I always seemed to be firing too late.  

[Barnacles]

Here's a video of what I mean. 
 

This was captured on a 60hz monitor, I think you can see the reactions to the inputs are of a far lower refresh rate. Is this normal for CloD, or is there possibly a problem with my setup? I have no similar problem in any other game requiring a joystick.

The control surfaces don't move smoothly too. Is this normal?

15 minutes ago, Yardstick said:

I don't know if it just a delay in the cannon sounds on the 109s or they just have a slow response but there appears to be a c. 0.5 sec delay between pressing the trigger for the cannon (s) and them firing.  I've had to adjust my timing of snap shots to reflect this as I always seemed to be firing too late.  

Yeah I see this too.

But the guns seem to fire instantly, there's just latency in the sound

 

[DD_Arthur]

12 minutes ago, 71st_AH_Barnacles said:

The control surfaces don't move smoothly too. Is this normal?

That’s all part of the charm......?

[Barnacles]

7 minutes ago, DD_Arthur said:

That’s all part of the charm......?

Well, I'll be diplomatic here and just say I hope eventually they polish these rough edges off the diamond I think this game can be.

But it's borderline unplayable for me right now.

Maybe it's something I can get used to, but it'd be absolutely wizard if they could fix it.

[DD_Arthur]

Have you checked out the movement of the cockpit stick animation yet?

[Barnacles]

2 minutes ago, DD_Arthur said:

Have you checked out the movement of the cockpit stick animation yet?

Yeah it's juddery.

 

[Rei-sen]

6 hours ago, 71st_AH_Barnacles said:

It seems there's a slight delay between my control inputs and when they're reflected in game

It's not a delay, IMO, it's the inertia of a big and heavy aircraft. Not that RC model feeling of a BoX planes.

 

This is one of the things that I like in CloD.

Edited August 12, 2020 by Arthur-A

[LLv34_Temuri]

5 hours ago, 71st_AH_Barnacles said:

This was captured on a 60hz monitor, I think you can see the reactions to the inputs are of a far lower refresh rate. Is this normal for CloD, or is there possibly a problem with my setup?

For me, the Out & In bars do not jump like that. They move smoothly.

[LLv34_Flanker]

S! 

 

Smooth inputs for me as well. Do you run the game in native Windows 10 Mode? I set my Launcher64.exe to Windows 7 compatability Mode and all good. In native mode menus were sluggish and inputs delayed in setup. 

[9./JG52_J-HAT]

JU 88C-4 Trop/Late when damaged shows life raft texture mapped to the underside of the motor gondola.

[Barnacles]

5 hours ago, LLv34_Flanker said:

S! 

 

Smooth inputs for me as well. Do you run the game in native Windows 10 Mode? I set my Launcher64.exe to Windows 7 compatability Mode and all good. In native mode menus were sluggish and inputs delayed in setup. 

OMG that worked!

Kiitos!

6 hours ago, Arthur-A said:

It's not a delay, IMO, it's the inertia of a big and heavy aircraft. Not that RC model feeling of a BoX planes.

 

This is one of the things that I like in CloD.

Nah, it's a bug. See above.

.
And anyway, control surfaces are designed to be as light as possible; I'm not talking about the delay in the aircraft moving, I'm talking about the delay in the control surface moving.

Anyway, it looks like this was not working as intended, and can be rectified by setting Launcher64.exe to Windows 7 compatibility Mode .

 

 

 

 

 

@Buzzsaw, just tagging you because this was quite a weird bug.

Edited August 12, 2020 by 71st_AH_Barnacles

[Rei-sen]

Oh, you meant the control surfaces delay? Luckily, I don't have that issue. Glad you've solved it!

[Enceladus828]

Some things I've noticed are:

1. The tail section of the Ju-88 is detachable after only a few hits, especially with a Martlett and Hurricane IIc.

2. A Minor thing, but in this video at 1:29 the guns are manned, however in the game they're currently not. Just thought I'd point that out now, rather than later.

https://youtu.be/iYBNCrCAHDs

3. Error with Macchi C.202 Serie III prop.

Edited August 12, 2020 by Enceladus

[9./JG52_J-HAT]

Bf 109F-4 online after taking damage shows a texture near the left flap that shouldn't be there.

[9./JG52_J-HAT]

Weird smoke coming out of a plane, as mentioned in one of my previous posts.s

The smoke stopped coming out after a while and was intermittent before that.

 

Dont't think it is supposed to be like this.

[FTC_Karaya]

2 hours ago, J-HAT said:

Bf 109F-4 online after taking damage shows a texture near the left flap that shouldn't be there.

 

Thats the impact bullet marker. Seems like you were hit in that exact spot at a very oblique angle, from dead six most likely. That will cause the marker to look elongated like that.

[69thSpiritus]

@J-HAT

 

Thanks, smoke bug is known, really hard to track that one down. We are aware of it. Also your post above it, that is a "small decal" element that is added to the planes when it it hit by small cal rounds, sometimes it has little errors like that square impact and sometimes it will paste them on actual DM holes. 

 

Like Karaya said, the ballistics... the graphic/texture needs tweaking. 

Thanks 

[Buzzsaw]

5 hours ago, Enceladus said:

Some things I've noticed are:

1. The tail section of the Ju-88 is detachable after only a few hits, especially with a Martlett and Hurricane IIc.

2. A Minor thing, but in this video at 1:29 the guns are manned, however in the game they're currently not. Just thought I'd point that out now, rather than later.

https://youtu.be/iYBNCrCAHDs

3. Error with Macchi C.202 Serie III prop.

Thanks for reporting this... when does the prop issue appear?

 

What throttle setting were you using?

The guns are not manned unless you select that option in your config files.

 

Re. Ju-88... will look at it re. Martlet.  In the case of the Hurri IIC, that is another matter.

 

Four 20mm firing at convergence will make a mess out of anything.

On 8/11/2020 at 4:29 PM, 71st_AH_Barnacles said:

Here's a video of what I mean. 
 

This was captured on a 60hz monitor, I think you can see the reactions to the inputs are of a far lower refresh rate. Is this normal for CloD, or is there possibly a problem with my setup? I have no similar problem in any other game requiring a joystick.

The control surfaces don't move smoothly too. Is this normal?

Yeah I see this too.

But the guns seem to fire instantly, there's just latency in the sound

 

The type of joystick problem you are showing usually appears when the players joystick is experiencing spiking or deadzones.

 

Have you calibrated the joystick in windows?

 

Right click on the Windows icon in the lower left. Type into the search box: "Control Panel"

The go to "Hardware and Sound" and click on "View Devices and Printers".

Now right click on your joystick, and select "Game Controller Settings"

Then select "Properties"

Click on the "Settings" tab, then on 'Calibrate'.

Follow the directions and click 'Finish' and then 'Apply'.

--

Now exit and start your game.

Go to Options, then Controls.

Go to Category 'Aircraft', and select 'Axes'.

Then select the control surface you want to program. In this case Ailerons.

Right click on the Command Box and then move your joystick to the left. The game will recognize the axes.

Below you will see Sensitivity and Deadzone settings as well as 'In' and 'Out' showing where the joystick reads.

[Hot_Rod]

Not necessarily a bug, but I believe it’s an error.  The waypoint action for the friendly flight in the two dogfight missions (“Blue - Dogfight #1“ and “Red - Dogfight #2”) on the Tobruk map are set as “Normal Flight” (it should be “Engage Fighters”).

I copied these missions into the FMB and changed the friendly waypoint action to “Engage Fighters” - this made a BIG difference in the aggressiveness of the friendly AI.  The “Normal Flight” setting makes your AI wingmen much more interested in maintaining formation with you than engaging the enemy fighters.  

 

The enemy waypoints in both missions are correctly set for “Engage Fighters” throughout the mission.
 

 

Rod

[ATAG_SKUD]

On 8/12/2020 at 3:04 PM, LLv34_Flanker said:

S! 

 

Smooth inputs for me as well. Do you run the game in native Windows 10 Mode? I set my Launcher64.exe to Windows 7 compatability Mode and all good. In native mode menus were sluggish and inputs delayed in setup. 

When I tried this Win 7 compatibility my plane would not "Create" in MP. It just did nothing. Went back and unchecked it and it worked normally.

skud

 

[jollyjack]

Hi, i tried to find them, where are they located?

[I/JG54_chuishan]

Just installed the updating patch, having issue in sound effect for all the cannons. In external view I can hear the cannon firing, but in cockpit I can only hear machine guns.

 

I notice all the cannons suffer from a serious sound volume reduction. The volume is way lower than machine guns in the cockpit.

[9./JG52_J-HAT]

17 hours ago, 69thSpiritus said:

@J-HAT

 

Thanks, smoke bug is known, really hard to track that one down. We are aware of it. Also your post above it, that is a "small decal" element that is added to the planes when it it hit by small cal rounds, sometimes it has little errors like that square impact and sometimes it will paste them on actual DM holes. 

 

Like Karaya said, the ballistics... the graphic/texture needs tweaking. 

Thanks 

 

Thanks, Spiritus. Glad to know it is being looked at.

 

[9./JG52_J-HAT]

Is this a bug? Was working fine before the update. And the update was the only change.  I still couldn't find any cause, though.

Files integrity has been checked with Steam. No joy.

 

 

[blockheadgreen_]

Had sound bugs with the guns/cannon. In the cockpit with each press of the trigger the sounds get quieter until silence. German cannons have no sound at all.

[69thSpiritus]

@J-HAT

 

Is this still happening and if it is is it just on a particular plane? Everything is fine on my end. Maybe try to change your resolution to 1920x1080, exit, launch, then exit again and delete the cache in mydocuments. 

 

Then play and see what happens. Then bump your resolution back up (again, exit after relaunch and delete cache). 

 

Sound issues has been noted, thanks. 

[Enceladus828]

18 hours ago, Buzzsaw said:

Thanks for reporting this... when does the prop issue appear?

 

What throttle setting were you using?

 

Well... I was flying the Wellington when I took that image-- just wanted to see what happened to the attacking aircraft when I noticed this.

The Macchi is damaged with Engine components such as Oil and Water Radiators/Lines, etc. likely broken, and throttle at ~half engine power.