Patch is live!The update to fix the P-47 and Lavockin take-off acceleration problem has now gone live! Just press update to get the latest patch. With this update these fighters can now take-off like normal even from the very short airfields in the Ardennes map. Do note that a P-47D with 100% fuel and 2x 1000 lbs will need full WEP and 20-35° of flaps at these fields. It's still a very heavy bird, especially when laden with bombs. (lift off at 116 mph with bombs and 20° flaps)
Tip of the day 1: The P-47's are great for escort, bomber interception and fighting above 20000 ft, but lacks in performance at lower altitudes. It's still a good plane for dive bombing and strafing though when the area is clear of bandits, or if you have a wingman to clear you. Use it's superior dive speed to outdive enemies on your six.
Tip of the day 2: The Lavochkins are very competitive energy fighters below 10000 ft. It's Bst2 Take-off power (Vzletnyy Rezhim) has it's peak at 6000 ft. As such try to lure the fight down when flying one, or try to force the La's to high alt if encountering them. Above 20000 ft they will struggle significantly vs most late war planes.
Fuel systemI found some weeks ago that the fuel system has a bug. Even if you get fuel leaks in 2 out of 3 fuel tanks, the airplane will still be able to fly for as long as if you had all three tanks intact. The fuel drain from the remaining tank(s) doesn't increase to compensate for the now empty tank(s), but instead the airplane has it's total fuel consumption lowered. This bug must have been in Warbirds for countless of years, probably even before I started playing. I found it when playing around with the ".hurtme rightfuel" and ".hurtme centfuel" etc command in free flight, noting that the total fuel burn seemed to be different before the leak vs after the leaking tank was empty. Using a stopwatch I could confirm this.
Ient tried to fix this and implemented a new code into the previous update, but the code must have had an error as instead all the tanks now leak into each other, which isn't quite right. I guess sorting out the bugs to make this game great again can be like eating a medicine, it might sometimes taste bitter for a short time but will soon permanently rid your body of the disease. Thank you Jlordj for notifying on this fuel issue, and just keep the feedback coming as we will try to fix any errors asap. I luckily spotted this side effect within a day of the last update, and Phil has already volunteered on the task of fixing the fuel system code. We should hopefully have a more realistic fuel system than before in very short.
olddog wrote:
Barely flying mostly RL, having major issue with sudden game freezing, video locks sound continues with an unpleasant buzz and I have to use the power button to exit, random, checked drivers sound and video. All up to date.
Haven't played much in so long feel like a newbie again.
That said thx for trying...
<S> Olddog. If you have a PC then you might have a problem with the windows update (the wauserve service). This must be the crappiest piece of code ever written, and I first noted it half a year ago. I actually had to disable it in both my PC and laptop, and have had to disable it on several of my friends computers. The Windows Update is normally always running in the background, and can consume half or more of your CPU's capacity. There's a very easy way to check this.
Close all programs, as your PC should then only be using only like 5% of it's CPU. Right click on the bottom task bar and open the "task manager". In the task manager, check the performance tab. If your CPU is running at 40-60% even though you don't have any games or videos running (it should be below 10%), then you most probably have the windows update bug, and this will eat your PC's performance, possibly making your games freeze.
If wanted you can make sure it's the windows update by choosing the information tab in the task manager, make sure you have "show processes for all users" enabled, and scroll down to the svchost.exe processes. These should be at 00-02 CPU usage, but if you have the windows update bug then one of these will be at 40-60 CPU usage.
To solve it: In the windows search option: write "services.msc". Open the services.msc program and scroll down to Windows Update. Right click it and choose properties. Set the start to manual (not automatic) and also stop the process from running. This should free up a lot of your available CPU, and you can simply manually check for updates once every month. Sometimes it is switched on by itself after a month or two, but just repeat the above process to have your PC running smoothly again.
<S>
/Robert
Register
Login
FAQ
Search
