did you rerun the DOTNETFX40.exe and also the Direct X9?

.
A old bug in Blac death track the poor soldier in the Bofor gun look at the picture it must hurt him a lot.
http://s8.postimage.org/d9kwjuuit/sh...006_154801.png


:rolleyes:

Unfortunatelly, this LOD bug still remain. It's annoying, because the conf.ini meshshowlod=1 solved this problem, but my PC drop 10-15 fps even on a small server :/

Pls devs, fix this bug, this would improve lot of running performance!

There are two bugtracker tickets with 95 and 25 vote, this is a common bug! (Many member complain about it on a hungarian forums too).

http://www.il2bugtracker.com/issues/153
http://www.il2bugtracker.com/issues/294

http://www.pumaszallas.hu/Private/VO...cs/LOD_bug.jpg

Sorry for the off topic, but, Tom, what's the small black square that is on your last picture? That on the low - left corner, close to the throttle, pitch etc levers? How do you activate it at the game?

Cheers

I've done a few single player quick missions against beaufighters, and they also have wheels down every so often. They do not always have wheels down, but sometimes they do. I've never seen both wheels down at once, usually one or two - and only after the plane has been hit.

Hi.
(Right click in the game, new info window, Alt+click on it, then right click and choose the customize info window).
After that choose the "Controls Feedback - Directional" component.

OK thanks

the 109E4 shows different oil temperatures to the E3 and E1 at the same power and radiator settings.while the E3 and E1 keep temperatures at 60° with fully opened oil radiators and full power, the E4 stays on the edge of 80°....i dont know if thats a bug of the gauges, or if it has indeed different temperatures.

ata pressure drops, as soon as your revolutions go above 2200 rpm in all the 109 variants.
if you watch closely, you will notice that at 2200rpm or lower and full throttle, the ata will be at 1,35 or at 1,45 with Notleistung...but as soon as you go above 2200rpm, it will decrease to 1,34 or even lower without,- and 1,44 or even lower with Notleistung.
again i dont know if thats a bug regarding the gauges, or if its indeed in the FM.

the turn and bank indicator doesnt seem to be fully functional in the 109s the first few moments after you have spawned...at least i noticed it on airspawns in multiplayer on rebka4 for example...while the slip ball seems to work, the bank "needle" stays in center regardless of attitude in the first few seconds.only after a certain amount of time, it will begin to work.

the prop pitch is still to slow ever since.while it should take only 4-6 seconds for a full revolution on the gauge, it takes 6seconds in every situation...thats wrong.

109 is still too slow...while it should get to at least 475kph at 1,35ata at sealevel now it hardly reaches 470kph at 1,45ata...

109cockpit....the display for your weapons in the 109 should be iluminated with green light to confirm that everything is ok...only if the amount of available rounds decreases, it should switch to a red light(as it does now).

textures....now with this patch, as soon as i reduce the textures from original to even high, the warning on the wings on the 109 which states: Nicht Betreten gets very blurry and unreadable...
the crosshair becomes less and less visible, and if you set textures to medium, it becomes indeed invisible.

i made already two entries for this issue, but now due to further testing, i came to the conclusion, that the B-Beobachtung(Observer) bullets just lost their explosive effects.thats definitely wrong.

maybe thats something to do with the fact, that you now cant blow up those fuel storages in industrial areas Luthier???
before this patch, it was indeed only possible to blow them up with only MGs, if you had B-Beobachtung in your belts...
if that is the solution to make a more correct damage model for those fuel storages, then thats indeed the wrong way....

decals for small calibre hits are still missing....or do I have to change sth. in the settings? cant play with my PC atm, just testing with my laptop on medium settings.

Can anyone confirm that small calibre hits are still not drawn?!

apart from that the overall smoothness is much improved with my laptop! good work gents!

Launcher crashes 100% of the time, shortly before the mission loads. I have repeatedly attempted the update, reinstalled Direct X, reinstalled .NET 4.0 (from the redist folder), removed my newer V C++ and tried the one in the redist folder, cleared the cache, manually placed files in each location etc. I'm on Win XP 32bit, and have no issues running the official version.

Event Type: Error
Event Source: .NET Runtime 4.0 Error Reporting
Event Category: None
Event ID: 1000
Date: 10/9/2012
Time: 2:31:22 PM
User: N/A
Computer: *********
Description:
Faulting application launcher.exe, version 1.0.0.0, stamp 4d6e3d08, faulting module core.dll, version 0.0.0.0, stamp 50659306, debug? 0, fault address 0x000e6c65.

For more information, see Help and Support Center at http://go.microsoft.com/fwlink/events.asp.
Data:
0000: 00700041 006c0070 00630069 00740061
0010: 006f0069 0020006e 00610046 006c0069
0020: 00720075 00200065 006c0020 00750061
0030: 0063006e 00650068 002e0072 00780065
0040: 00200065 002e0031 002e0030 002e0030
0050: 00200030 00640034 00650036 00640033
0060: 00380030 00690020 0020006e 006f0063
0070: 00650072 0064002e 006c006c 00300020
0080: 0030002e 0030002e 0030002e 00350020
0090: 00360030 00390035 00300033 00200036
00a0: 00440066 00620065 00670075 00300020
00b0: 00610020 00200074 0066006f 00730066
00c0: 00740065 00300020 00300030 00360065
00d0: 00360063 000d0035 000a




*****

Event Type: Error
Event Source: .NET Runtime
Event Category: None
Event ID: 1026
Date: 10/9/2012
Time: 2:31:41 PM
User: N/A
Computer: ****************
Description:
Application: Launcher.exe
Framework Version: v4.0.30319
Description: The process was terminated due to an unhandled exception.
Exception Info: System.AccessViolationException
Stack:
at <Module>.corelib.RenderWorld.Render(Boolean, Boolean, Boolean, Boolean, Double, Double)
at maddox.core.WRenderWorld.Render(Boolean, Boolean, Boolean, Double, Double)
at vyXPxPXK6qtT2JHtn7W.oF8cKOXlBfDuHiT4EgV.DyjcDmCq9b v(Boolean)
at vyXPxPXK6qtT2JHtn7W.oF8cKOXlBfDuHiT4EgV+JmTo5OXzMw A9EmAfAKk.uliXwTdI3VbVcqUROuYr(System.Object, Boolean)
at vyXPxPXK6qtT2JHtn7W.oF8cKOXlBfDuHiT4EgV+JmTo5OXzMw A9EmAfAKk.render()
at fqUEJHFbcMMmuBqa6LK.4S1nwK7z21Ly9mYxPwE.QrUnlsy0il c()
at fqUEJHFbcMMmuBqa6LK.4S1nwK7z21Ly9mYxPwE.MbNnlVgfg3 u(Boolean)
at ceEPOavDO8OTFwFnCnX.hrZUcnvrFFUPa8qH5Ii.dGdhXOXhfr 9LCN84s7u(System.Object, Boolean)
at ceEPOavDO8OTFwFnCnX.hrZUcnvrFFUPa8qH5Ii.hVuJhI9Da5 (AZAKS3AEO5F0ZUdYNA9.Q0jqMCADgLe2tQDtS9O)
at ceEPOavDO8OTFwFnCnX.hrZUcnvrFFUPa8qH5Ii.p8u9RxClFE ygk4ssMyR(System.Object)
at ceEPOavDO8OTFwFnCnX.hrZUcnvrFFUPa8qH5Ii.HMDJJU7HJl (AZAKS3AEO5F0ZUdYNA9.Q0jqMCADgLe2tQDtS9O)
at ceEPOavDO8OTFwFnCnX.hrZUcnvrFFUPa8qH5Ii.bajJpZVOmt (System.String)
at xPW984J2CbB6GNlqet0.gwDsDSJdID5e8aYY9Ka.MissionLoa d(System.String)
at ZIfAD49Z7ds5I7Rir6A.iaVYEV9SQk2F93rCdgV.jPvnoorJU5 L()
at System.Threading.ThreadHelper.ThreadStart_Context( System.Object)
at System.Threading.ExecutionContext.Run(System.Threa ding.ExecutionContext, System.Threading.ContextCallback, System.Object, Boolean)
at System.Threading.ExecutionContext.Run(System.Threa ding.ExecutionContext, System.Threading.ContextCallback, System.Object)
at System.Threading.ThreadHelper.ThreadStart()


For more information, see Help and Support Center at http://go.microsoft.com/fwlink/events.asp.