[DBS]TH0R

Apparently he says no spiking due to hall sensors. Lets define some terminology here. What is "full power": 1.4 ATA or higher? How far back do you deflect the stick? 1/3, 1/2 or almost all the way back? What speed and altitude do you enter the turn? Like others here, I experienced no such behavior. I can ride the stall all day long and anticipate it well before it happens. Aileron control is not decreased and recovery for me is simply letting go of the stick. Please provide a track or better record a video explaining in detail what is wrong with the FM in this regard.

I can ride it near stall all day long. I too can't find that behavior, perhaps too much influence of other sims? Would love to see the track or video explaining this in detail.

I presume you are referring to v1.2 @ 4K resolution? I have no problem running v1.2 everything on high with 30-40 FPS with my rig.

Your screen shot tells half the story. Rotate the plane at a different angle, point it towards you, paint it against the ground with a forest for instance - there were rendering instances in 1.2 that made a nearby plane almost invisible. Plus, last I checked A-10 is larger than smaller propeller driven A/C we have in-game. And you're running 4K. :)

Agreed. Flight sims were always a niche. Now that we have several to pick from - herein lies the answer. :)

Definitions are needed. How many players define a full server? Back in '46 days it was ~30. 150 could fill 5 servers. Besides, this is a moot arguments since quick action / dogfight servers are just one flavor of MP game play. The rest being dedicated historical missions and campaigns like SEOW where the real MP fun is. Point being? I am aware of the fixes TF did to the game. That. :thumbup: Seconded. BoS renders a 2 engined plane at about 9.5 km, and single engined at just under 7km. That isn't saying it is easy to spot them at those ranges. Quite the contrary.

Might be. Tough if you could spot objects before you did not have that problem. Having it as an option is just fine as it is - helps those that couldn't.

Please define "a few" for me. Two or three Sundays ago, ATAG had 100 pilots (full), and SoW had 50+. Both running so called "full switch" settings. And that is just CloD. With other available servers having "a few" pilots. ;) Perhaps you are missing peek hours.

Zooming alone isn't an issue. It is welcome and mandatory in a flight sim. Zooming becomes an issue when it is the only way of spotting something in the vicinity near you where you would be able to spot it in real life without a problem. I respectfully disagree. Definitely not on pair with other flight sims at the moment, that much is true. But there are more than plenty of them. Numbers will rise exponentially once Normandy map is out. And that is why this feature / fix was requested.

Perhaps you should try with a 24" screen (or smaller) and do some WWII dogfight to see where the problem really was/is. If you dislike it, turn it off. EDIT: Unless you're running 4K, 55" screen with a 1080P rezolution has 40.05 PPI. 24" screen has 91.8 PPI. The difference is obvious. In other words, it is you who had the advantage over others in spotting since the pixels were rendered larger.

Seconded. I can't tell if I am naturally gifted (most definitely not lol) but I do know what I saw with my own two eyes earlier this year from 10-11 km high when I flew to Duxford Flying Legends - cars on the highway. Having this feature, as an option, is realistic. I do realize some people do not have good eyesight. There are hardware differences too. Being it an option is great. Hats off to ED for listening. One thing to remember though, there is a difference in being able to see (i.e. render) and being able to spot things. ;)

So that is a no on the link then? Hey, if it helps to sugar coat the facts (i.e poll results) go with it. :)

Seeing how this was requested by vast majority here, especially those focused on WWII prop jobs. I thank you ED for providing an elegant solution. I haven't seen that announcement. Care to share a link please?

And some allied pilots said in their interviews that they feared 190s, not 109s. All of those comments need to be put into context, when, where and how (which year, plane model and which skill level). Longer stick helps many of us here, so if its not the violin, it is the violinist then. ;) Got no intention entering into another debate with cherry picked data. You haven't proven anything, yet. Since I have no problems with how 109 is modeled (and is being polished) the burden of proving things is on you. End of OT.

Well, some pilots did comment that 190 was "more maneuverable". :smartass: Tried with a longer stick? I got no such behavior in 1.2.6 (haven't yet installed 1.5). Very mild for me. And the thing is a rock solid firing platform. The only jerkiness I got was when I was manhandling it. As for the latter, this is only your opinion, not fact. Be careful not to start sounding like a broken record.

Funny how DCS isn't the only sim that doesn't have 0 for level flight. ;)

Not to mention F model was almost completely phased out in the second half of '44.

Great, thanks!

I stand corrected then. :)

Hog was 40$ without discount. I guess everything has a higher price nowadays. Congratulations on the release, I will definitely be getting it down the road some day, after more info and initial impressions.

Agreed. Would be day 1 purchase for me since I find it the best looking modern fighter to date. I'll wait for now.

According to DCS Product Terms it should be EFM, but after reading the description it looks more like PFM??

Done. :vertag:

I noticed your comment but was unsure what exactly you meant by it. Thanks for clarification. Can we hope for a fix in not too distant future, development time permitting of course?

I was about to ask a question whether anyone else things we're spamming this thread, however I am not interested in an answer since it would lead to OT. IMO everything has already been said and evidence provided. I don't know of a better way of backing up what I have seen with my own eyes other that with what was already posted here. It has been years since I first reported this bug, if nothing else I am glad others see it too.