Winston60

I've looked into this a bit and found that the new Su-27 template has new/different textures for the nose borts. Here's what you need to add to your description.lua file for each of your old 3rd party skins to get rid of the nose bort numbers:

You are correct Sir. The bort numbers are porked in all older skins. I think this is something the 3rd party skins makers will have to look into.

1 through 5: I'm not trying to say they didn't have the proper info once, or doubting that they have their own experiences in high performance aircraft. The DCS P-51 wasn't broken here until just recently. A few patches back it was fine. Now it's broken. I'm saying that right now the DCS P-51D's engine and cooling systems modeling is wrong, be it intentional or by bugs. The poor OP is trying to take a badly bugged aircraft through a high performance climb scenario in an airplane with a severe disability. Maybe he should wait and try again after the promised bug fixes are finally released to us. You are just arguing for the sake of argument. Knock it off and face the facts. It's broken!

1: Based on personal experience, 2-1/4 hrs in a 'back seat' P-51D conversion. 2: Hmmmmm...... Why don't we have this yet? (One patch already released since we were told it was fixed.... internally) 3: You couldn't be more wrong. A P-51D in good repair can climb all day at 46 inches of MP and 2700 RPM at 170MPH on full auto rads and never approach coolant or oil temp red lines. Been there, done it. 4. In single player, eminent engine failure is warned by various sounds and the engines performance gradually degrades in power and RPM. In multiplayer there's no warning sounds, no reduction of power or RPM... the engine just abruptly seizes. You don't need a track. Just jump into any single player mission and abuse the aircraft. Then jump into any multiplayer mission and do the same for the same amount of time. You can't miss the difference. 5. I don't think so. We're talking about performance here right? An interesting short read on P-51 flying. http://www.warbirdalley.com/articles/p51pr.htm

There's just too many things wrong with this aircraft in the current release. It used to be fine but later patches have broken it severely. Better to wait until they fix this 'super-bugged' aircraft. * Performance is less than actual specs. * Oil viscosity is wrong, hence the oil pressure bug. * Temps go too high on auto-radiators. Totally wrong. * Engine failures are different in single player vs. multiplayer It's really a shame to have once had a fairly good flying and performing P-51 in DCS World but since these bugs were introduced the Mustang is no longer a valid aircraft in this simulator, IMHO. Hoping for better days.

It's no longer available in the user files downloads. Does it still work in the current version of DCS?

Thanks LeVince, I posted the problem over there. This is most easily noticed when there's an AWACS around. With the Phantasmagoria on you can't filter out the AWACS. I'm pretty sure this is a bug and just recently started happening.

This is most easily noticed when there's an AWACS around. With the Phantasmagoria on you can't filter out the AWACS.

You must set your "TV target frame size" to the appropriate size of the target you are trying to lock. For example, if you have it set at 60.. it will not lock a vehicle. A vehicle requires the size of 10. See page 72 of the FC3 manual or page 30 of the Su-25T manual.

When switching on the Phantasmagoria pod, I can no longer filter the Beryoza SPO-15LM RWS receiver. By pressing RShift R (RWS Mode Filter as explained on page 213 of FC3 Manual) I can usually turn off the indications and sound of all emitters operating in acquisition mode. If I switch off the Phantasmagoria I can now RShift R and the RWS filter works properly; it only picks up lock and launch lights and sounds and does not constantly indicate emitters operating in acquisition mode. Why can't I filter out the RWS's detection of emitters in acquisition mode with the Phantasmagoria pod in use?

When switching on the Phantasmagoria pod, I can no longer filter the Beryoza SPO-15LM RWS receiver. By pressing RShift R (RWS Mode Filter as explained on page 213 of FC3 Manual) I can usually turn off the indications and sound of all emitters operating in acquisition mode. If I switch off the Phantasmagoria I can now RShift R and the RWS filter works properly; it only picks up lock and launch lights and sounds and does not constantly indicate emitters operating in acquisition mode. Why can't I filter out the RWS's detection of emitters in acquisition mode with the Phantasmagoria pod in use?

P-51 engine damage model is porked in multiplayer. May have something to do with the high oil pressure bug. Some patches back I could fly 1 hour plus at the "all day" setting of 46 inches and 2700 rpm, but now I get random engine seizures at that setting. ED is aware of this oil pressure bug. Once it's fixed hopefully engine reliability and the "all day" engine setting will return.

Is this high oil pressure bug why I cannot now fly constantly at 46 inches and 2700 rpm without the engine seizing?

How about bugs: * Pulling "g's" sound bug * CBU-87, CBU-97 falls short in CCIP mode * Autopilot modes stay on HUD even with EAC off * Bug in PAC; In single player nose trims down immediately when cannon is selected instead of when cannon is fired. In multi player PAC doesn't work at all. Have they fixed any of those? (nearly 18 months old for some of those bugs)

It's not the reflections that are disliked, the reflections are great.... it's the dirtiness/opaqueness of the glass.

It should make a liquid pumping/grinding sound to let you know fuel is being pumped from a refueling vehicle into your plane. All DCS aircraft have this sound when you rearm/refuel. It's really irritating and awful sounding at default levels, I've edited the gain in my game to cut down the volume and have finally gotten used to it. Now it's strangely absent only in the F-86. I'm really angered and surprised at how many more things they break with each new patch! They seem to fix one thing but break a few others. One step forward and three steps back. Quality control and testing seem to be Belsimtek's weaknesses. :badmood:

I now believe that this excess gun smoke is caused by the changes to the grey smoke that comes from the three smokestack factories on the ground (the two smokes come from the same graphics file/routine. This new ground smoke is awful and devastates frame rates when flying near it or through it. Maybe this is not Belsimtek's fault but the ED's fault for introducing the horrible new ground smoke.

You think this new smoke effect reduces your framerate when you simply look at it... try flying through it. My frames/sec go from 60 to single digits! I believe it's also the cause of the Sabre's problem of an obscured gunsight when the guns are fired. Funny ED doesn't respond to this issue. Do they even know about it?

So here it is nine months since the last post in this topic and it seems like some of these problems are still in Dec 2014's ver 1.2.14.35605 I've never seen ED respond in this topic to any of these bugs so I'm guessing they don't realize these bugs exist?

I just noticed that in ver 1.2.14.35605 you can no longer hear the sound of the refueling process in multiplayer. Haven't checked single player. Can someone verify this?

Hold the starter longer. Now it takes a much longer cranking before the engine fires. If in a custom mission, make sure if the outside temp is low, you might have to dilute the engine oil.

From the first release I've never had a "trim reset" key on the Sabre (English version). :huh:

You are correct, in mission builder, setting 100% fuel gives actually 97% in the aircraft. Workaround for rearming/refuelling bug...... move fuel slider to only 97% fuel; then rearming will take place.

Opinions please: I like the new reflections somewhat, but I think vision is generally just too bad now. Anyone agree? or disagree? I hope someone mods this back to a more clear/clean canopy. How about the dramatic addition of more smoke when firing the guns? Now I can't see what I've just shot at!

Yes, verified. Mine is exactly as shown. I do not own the Bf-109.