Describe issues with BOB COD that need patch - for Oleg, Luthier

[Rickusty]

Since Steam updated with the latest patch,
the game crashes a lot... But... The first thing is: the first mission (just a randon one) always loads. Either from the QMB or in the FMB.
Then, it can happen that the 2nd or 3rd time, when there's the loading bar
on the bottom of the screen, the game crashes without apparent reasons...

It happened really rarely before...


My system
-------
E7500 c2d 2,96mhz
4 gb ram ddr2 800mhz
Nvidia GTS 450 1GB
Windows 7 32bit

[335th_GRAthos]

Bombs need some serious patch!

#1 Get these jumping jack bombs fixed ASAP !
What kind of rubbish is this ? Read the IL2FB manual on how bombs rebound based on a.) hardness of the soil and b.) deflection degree and apply it!
They way bombs jump all over the place is completely unrealistic.

#2 The SC250 bomb on the Bf109E-3B seems not to be exploding. Exploding probability is less than 20% percent. Whetehr you dive-bomb, high-alt bomb or skip-bomb.
This is rubbish of course (same as the "charging time 8 weeks" on the bomb loading menu but, it makes me wonder).

It would be good if somebody publishes some more information about the bombs and the conditions under which they may fail to detnate because I fail to understand the logics for the sc250 of the BF109E-3B.
(on the ME-110 with 2xSC500 I have no issues at all).

~S~

[Gromic]

Also having stability issues since the second patch (which increase frame rates for me massivly). With a process viewer (sysinternals) running on a second monitor, I can see that launcher.exe never frees mission memory when exiting a mission. It keeps adding more memory with each flown mission thereafter until it gets to around 2,5 gigs allocated and then will either CTD or cause a complete reboot of the system altogether. The only way I've found to avoid it, is restart the game once launcher.exe surpasses 2 gigs used.

Launcher.exe needs to free mission memory upon mission exit.

[335th_GRAthos]

Having done some further testing I found out that:

The SC250 as well as the 4 x SC50 on the Bf109-3B are not exploding 90% of the time!
There is only one way to make them explode every time:
- Start a steep climb with the Bf109
- With the nose pointing sharply upwards, release the bombs
- The released bombs will continue their upward trajectory for a while and then fall downwards.
That's it, every bomb explodes!

The ME110-C7 with 2xSC500 has no problems
(I have not yet tested a ME100 with SC250s...)

I hope it helps to solve the problem.

Originally Posted by 335th_GRAthos

Bombs need some serious patch!

#1 Get these jumping jack bombs fixed ASAP !
What kind of rubbish is this ? Read the IL2FB manual on how bombs rebound based on a.) hardness of the soil and b.) deflection degree and apply it!
They way bombs jump all over the place is completely unrealistic.

#2 The SC250 bomb on the Bf109E-3B seems not to be exploding. Exploding probability is less than 20% percent. Whetehr you dive-bomb, high-alt bomb or skip-bomb.
This is rubbish of course (same as the "charging time 8 weeks" on the bomb loading menu but, it makes me wonder).

It would be good if somebody publishes some more information about the bombs and the conditions under which they may fail to detnate because I fail to understand the logics for the sc250 of the BF109E-3B.
(on the ME-110 with 2xSC500 I have no issues at all).

~S~

[Pudenfuhrer]

I'd rather not see changes to your vision of Cliffs of Dover - ie changing the way the rpm and carburretors work - and see the non working features fixed. Mainly I'm wanting the radio commands to work - which right now don't actually seem to do anything. I'd also like to see the campaign missions give more information, for example possibly some way of knowing what my number and callsign is prior to takeoff - oh and how many planes are in the flight etc. Right I get orders to engage enemies and also told to stay on my leaders wing - which is confusingand that's really not as immersive as it could be at the moment.

In my conf.ini I notice I am using the DX10_0 renerer - I presume basically DX9/10 - renderer. When I change that to DX10_1 it has black lines on the sea as a lot of people report and is otherwise identical. It seems to be a DX9/10 rather than 10.1/11 game just now - is this going to develop as things go on? I'd have thought tessalation would massively boost the possible performance or complexity of meshes for this type of game if it was implemented.

Thanks - really liking just flying about at the moment - hope some solid tactical missions come along soon
p