sobek

Which is a pretty big deal. You can't fix a bad connection though.

Good point, i never use those.

Dumb bombs and LGBs have AFM. JDAMS don't.

There could potentially be other things causing a reconnect, you know...

How can you even be sure of the cause of the disconnect then?

Just one or two posts ago, all European DSL users had this problem, now they don't? ;) I'm playing devils advocate here, but the point is, you are trying to make this issue look bigger than it is and that is not helping your cause. The way this usually works is that your ISP checks if you're connected for more than 24h and if that condition is met, you get disconnected at a certain time. If that is the case, you can manipulate that mechanism by setting your router to reconnect sometime in the early morning, which will lead to the aforementioned condition to never be met, so your ISP will never force the disconnect. Whether your ISP follows that protocol or forces a new IP on all clients at a preset time i do not know. I'd ask around the net how your ISP handles this. This practice was really common 10 years ago, less so now. Hate to tell you but your ISP sucks. Is there really no alternative? Btw. what does your modem log say exactly at the time of the reconnect? First level support is clueless, this is a given. They work through a set list of possible issues that cover only the most basic of problems. Did they never relay you to higher tier support? If your answer is no, then your ISP sucks even more than previously indicated.

I'm not a Telekom customer, i use UPCs DSL offering. Here's a thought though, you don't have to use your ISPs router. There's companies selling decent routers and they're not that expensive... Which one? I know of Starcraft, which halts the game completely for everybody if a player drops too many packets so that all clients stay in sync. That might be a little undesirable in servers with many players.

I'm on a DSL ISP in Europe and i don't have that issue, i only get a new IP if i tell my modem to reconnect. I never get forced to reconnect by my ISP. Please don't make it sound like every DSL customer has this issue, it is not the case.

Does anybody else even have this problem? It wouldn't make sense to implement such a complicated feature for only a handful of users.

What's taxing the CPU is making an AI that flies the PFM to the edge. The DM has nothing to do with that, it's as taxing whether an AI or a human flies the plane.

I don't think anybody wants to discredit your efforts, but the information needed to model this is hard data, description of the hardware and algorithms that run on it, test data under controlled conditions, etc. Unfortunately the info in the public domain is just puff pieces, telling you some stuff about what they do but not how they do it. Without knowledge about what algorithms are used under what circumstances, there is no point in even attempting a faithful model.

Halte ich für zunehmend unwahrscheinlicher. Sept sind nur mehr 1 1/2 Monate und man hat noch kein einziges mal eine FM Demo oder sonst irgendwas ausser Screens mit fehlenden Systemem gesehen. Vllt. täusche ich mich bzgl des Status in dem sie rauskommen wird, aber ich personlich glaub nicht daran.

Hinzugekommen ist auch die enorm kostspielige Wartung. Schwenkflügler sind einfach Geschichte.

Since nothing is clickable in there yet, what's the point of an english cockpit?

It's not the difference in pressure below and on the top of the wing. It's the difference in pressure before and while moving over the wing. If you expand a volume of air adiabatically beyond the dew point, condensation will occur. This is exactly what happens, there is a low pressure area on top of the wing that the air moves through, which causes it to expand adiabatically and compress again.

It does. The only time when flying full open makes any sense is when you wildly modulate engine power output, because the radiator door actuator is too slow to cope with rapid heat output changes. As is the case IRL. It does, which is why flying the rad full open at all times is a bad idea.

This is wrong. I've spent hours upon hours flying in all sorts of situations with the rad on auto and it worked. If you're referring to the green bar on the coolant temp gauge, it has no meaning, search the forum. But please don't perpetuate half truths about DCS not working correctly when you are misinformed. Same as in the other thread where you claimed that overboosting has no negative effect.

Now that is just bad advice. There's no need to keep the rads fully open during any phase of flight except if you expect *very* rapid changes in heat output in a short amount of time (like during takeoff).

The cause for the high peak pressure is primarily ignition timing. The timing for certain boost pressures is set to work with the RPMs that are stated for said boost pressures. Use lower RPM and ignition timing will be off. The torque output will be lower than at high RPM so there is no potential damage to the engine through sheer torque. It's the piston rod and crankshaft bearings that get hammered.

Humidity is already modelled, the flight model does tap into it if i'm not mistaken. Also this is more than just cosmetic. In WVR dogfights, knowing whether your opponent is pulling gs or not is important.

Never heard of that. Seems a bit weird since standard procedure for checking the prop governor is to run up the engine and cycle the prop lever between low and high RPM. Also i see no reason for the pitch adjustment system taking damage, as setting the pitch to full coarse shouldn't require significantly more torque than setting the prop to any other pitch. Knocking is a real concern for P-51 pilots and it is modelled in DCS. You not having killed an engine doesn't prove anything. Try flying 45"@2000RPM *for a while* and see how that goes.

The how is correct but the why is not. It has nothing to do with the prop governor but instead this procedure is used to prevent knocking. Less RPM means the engine can handle less boost because spark retardation is tied to the power lever setting. If you leave boost where it is and just decrease RPM, this may leave you in an operating condition where spark timing is much too early. This in term will lead to peak pressure occuring at or around the time when the piston is at top dead center, and this puts enormous strain on the piston rod bearings. Low boost is not a problem on the other hand (well this is not entirely true because underboost influences the piston ring seating and can lead to increased wear as well, but it's not as bad as knocking). Therefore one needs to ensure to never have the engine running at a boost setting higher than what is recommended for the set RPM.

That did not read like a normal question to me... And the things you state are, well, far fetched.

Or learn to handle the IC once all is in place?

You're right, i forgot that it is already in 2.0, my bad...