Strong05

I currently use a 4k tv as a monitor. I have VR too so I don't use the monitor much but when I do, DCS looks great at 4k on a 50" screen. I haven't noticed a discernible difference in spotting, despite a lot of people saying it will be worse. I leave MSAA and AA off. I used to have a triple screen 24" setup, and I much prefer the larger single 4k monitor to 3 screens. Plus dcs runs better with a single screen.

Just verified everything tonight. All my router settings are correct and updated firmware. Looks like I most have the new ipv6 protocol as I was able to connect via IP address to a server that didn't show up in the search results. Sorry if this doesn't help your issue.

Not sure if it's related but as of the latest update I only see about 6 servers. I usually see a whole heck of a lot more then that. Could be an ISP problem though as I also just moved... Figured I'd start here though. I'll also double check my router but I have a static IP in the DMZ so that shouldn't be a problem.

I believe this may indirectly answer your question (From wiki): Mode 1 – provides 2-digit octal mission code. (military only – can be changed in flight)[19] Mode 2 – provides 4-digit octal unit code. (military only – usually can't be changed in flight. Some aircraft like the C-17 Block 17 and higher have the capability to do so)[19] Mode 3/A – provides a 4-digit octal identification code for the aircraft, assigned by the air traffic controller. (military and civilian)[19] Mode 4 – provides a 3-pulse reply, delay is based on the encrypted challenge. (military only)[19] Mode 5 – provides a cryptographically secured version of Mode S and ADS-B GPS position. (military only)[19]

I have a somewhat similar setup (1070, with a 6700 @ 4.7). I have very few drops in frame rate and have the same settings with the following exceptions: MSAA=off visib range=medium terrain shadows=flat (on the right) disable aero interface checked Other things to consider: In DCS 1.5 cpu clock speed is king so that .5 ghz may make a difference. Ram speed does have an impact up to about ~3000mhz Your problem may be fixed when dcs goes to 2.5 (or if you have NTTR or normandy do you have the same problems?)

Cyph3r, This may have been asked before, but: Can the base be mounted to the same pattern of holes as the TM warthog base?

I had a triple screen setup, and now have a 50" 4k screen... neither of which I use anymore for DCS. The only time I use the big screen is to show something to an onlooker. IMO, spotting is no more difficult then on flat screens. It just takes time to learn what to look for. Now identifying the bogey is the hard part, especially in WWII plans. Hard to say if it's any harder then on a large screen or not though. Also, I believe dog fighting is much easier in VR due to the natural feel and understanding of where you are looking versus where you are flying. With track IR I could easily get disoriented as to where I was looking versus where I was flying.

How do you use it? I tried using it with the cold start instant action from Normandy and NTTR and it didn't appear to work. I probably wasn't using it correctly though.

Free Flight V1.0.miz Here's the mission with the hot ramp slots for the 109.

I'll take a closer look. I'll try to post the mission later today.

Pretty sure there is some kind of bug here. I made a mission in the editor and put the 109 on the ramp as a hot start. As soon as you spawn into the plane, within 5-10 seconds the motor dies. Doesn't matter what you do.

Possible... I'm still having problems keeping the motor alive. Not sure what I'm doing wrong but it blows not to long after takeoff most of the time. And that's using auto rpm/pitch and 1.2/1.25 boost. I think it has something to do with the auto radiator flaps.

Okay, think I finally figured it out. The manual specifically says not to let the engine idle below 600rpm. Which is what I was letting the engine warm up at to keep from sending the oil psi over redline. Apparently oil psi isn't an issue... this time I just let the engine idle at 600 long enough for the fuel psi to come up then revved it up to 1,000rpm with no regard to oil psi until both oil and coolant temps were in the green with the cooling flaps open. This method seems to work great.

The game manual specifically states not to let oil psi go above 9.75 (what ever that unit is in metric for pressure). I move the rpm up as quickly as possible while keeping the oil pressure below max. I was not able to get the oil up to temp before the engine blew (I think max rpm was 900, which was the most rpm oil pressure would allow). However, it does state to only hold 600 rpm for 30-45 seconds. Maybe oil pressure doesn't matter after that, maybe you can bring rpm up to 1000 after that warm up period? Or maybe there is a pressure release valve once rpm comes up? Coolant temp should be taken from the head or block of the engine not the radiators. So if you overheat the motor it should be indicated on the gauge regardless of flow to the radiators (unless the Germans do things really really weird and illogical). I haven't had a problem with a "warm startup". So I'm confident it's not my procedure, with the exception of a "cold weather start".

Just did the tuturial for start up... nothing sticks out as incorrect versus what I do. I'm using cold start instant missions on NTTR and Normandy. Both have the engine at around 0 C at start up. Seems very difficult to get the oil temp up. I'm thinking that might be the issue I'm having. Could the cold start lever possible help with this? Pingpong champeen: Cool dude, I used to live out there for a few years. Nice area and lots of airplanes to see.

So was able to start up and t/o without a problem from the VA 1.5 server. I did notice the temps were almost in the green even before startup. Where as the cold start mission from NTTR and normandy are much colder. I'm thinking that's where the problem lies. I did notice the motor seems to be very sensitive to coolant temps as the motor blew as soon as it hit the upper limit.

Thanks pingpong. Maybe it's worth mentioning I'm doing this in 2.1 not 1.5... Is anyone else having problems? I should also mention I used to have 0 problems flying the 109 from a cold start until this update. And holy cow WR AFB... that brings back memories.

That's interesting because I'm used to the Merlin and hardly ever have an engine failure with either the spit or the mustang and I constantly have engine failures on this thing.

The engine is dying before I ever exceed 600 rpm. And on the off chance I manage to take off I ensure that either I a: don't exceed 2500 rpm or b: have the governor set to auto and that I use slow throttle inputs so as to not overwhelm the governor.

Thank you! That explains why there weren't moving. As per the startup procedure in the manual though you aren't supposed to exceed 600 rpm on startup for the first 30-45 seconds or not to exceed 9.5 (or was it 9.75?) oil pressure. Maybe I'm not advancing the throttle enough on warm up after the initial 30 seconds or so...

Yes I have tried that. Although I will say the radiator flaps appear to be non responsive no matter what setting I place them in. I have tried startup with them in auto and open. Neither seems to have an effect. I will try to upload a track (will that work or do you need a video?).

Followed the manual to the letter and the motor blew up maybe a minute after startup 2 times in a row. Wasn't even able to get the temps in the green to taxi. I can't believe other people aren't having this problem.... Thanks again guys for the help.

Just followed all of this and babied the crap out of the motor and it still blew up about 3 mintues after takeoff. Engine was set to 2000 rpm with the auto governor on. What the heck??? Coolant was a little warm but still within the limits on the gauge. Radiator was set to auto.

Good point... manual says 10 and 30 minutes respectively for total rated time for those power settings not continuous.

Yes, but maybe not long enough... Temps are usually between the markers on takeoff. How long should you warm up the engine?