White Owl

Alright, so it's not just me forgetting how to do things. That's a little reassuring. I've never used snapviews because I use TrackIR. I'll take a look at the axis tuning, see if I can make it do what I want. Thanks very much. :)

So I've been away from DCS for a long while, and want to try out this newfangled 2.5 whatsit. Many things are new... but some old things are still there. I still hate the stupidly fisheyed default FOV limits, and want to adjust them. Back in the day, I would have edited server.lua, but that no longer works. Or I would've edited the individual plane's Views.lua, but that no longer works. I tried searching this forum, only to find a ton of threads from the past several years, no longer relevant. Please, how do I fix this? :helpsmilie:

There are lots of sim-pilots out there who I'm sure would love flying in DCS if they ever gave it a chance. But they won't try it, because they don't want combat. These potential customers like high fidelity simulations of complex aircraft, they like high performance flying machines, they like immersive cockpits... but they simply don't want to have to deal with getting shot at. I can't say I blame them. This missions generator sounds like a very good way to sell them on DCS!

It really bugs me that the ingame ATC doesn't take wind direction into account when assigning a runway.

The intro story is well written. For pure flying joy, the Sabre is probably my favorite DCS module so far, but good missions and/or campaigns for the plane have been scarce. Very much looking forward to this one!

Yes, some variety in time of day and weather would be welcome. Not having to care about wind direction in a relatively lightweight taildragger is as immersion-breaking as the GPS navigation.

I was thinking about this while playing tonight, since I had seen a bomber magically vanish in midflight once before, but had no idea what happened or how to go about reporting the issue. Just a few minutes ago, I was flying Blue and one other player was flying Red. Only two people on the server. I took off from Gudauta and attacked Bzyb. The Red player ran a reconnaissance mission over Gudauta. I saw the server message that an enemy bomber was inbound from Sochi-Adler to Gudauta. Very shortly after seeing that message, I destroyed the last ground vehicle at Bzyb. The server message reported Bzyb was closed. All perfectly normal and working as expected so far, right? The next server message reported a friendly transport moving to Bzyb. Almost at the same time, the next message popped up and reported the enemy bomber destroyed. I never spotted the bomber, let alone shot at the thing. I have no reason to believe the Red player shot it. Nobody else was on the server. So yes, I believe there is a bug at work here. It's certainly possible that captures could still happen with this bug. You just need an AI bomber or transport to complete its trip before some player triggers another event. I hope this report can be helpful somehow. Still enjoying the server.

In addition to the calls for more time between server resets, I want to request more notice before the reset. Tonight I was trying out the reconnaissance missions in a TF-51, and I lost track of time (my fault). Shortly after taking off for a fairly distant target, the 30 minute reset warning popped up. 30 minutes was only barely enough for time for the round trip. I managed to land with the intel at a friendly airbase, but the server shut down while I was rolling out, so I didn't get to deliver the intel. I suggest a 60 minute warning would be more useful in these slower planes. Maybe warnings at 60, 45, 30, and then every 5 minutes. Other than that, I'm enjoying the server. :)

The lazy eight maneuver demonstrated in your video is very different from the lazy eight I learned for my Commercial Pilot certificate several years ago. I learned it as two 180 degree turns, one to the left, one to the right, ending at the same altitude, heading and airspeed as you started. You climb and increase bank for the first half of each turn, then descend and decrease bank angle for the second half of the turn. The nose of the airplane draws a sideways figure eight centered on the horizon; thus the name. Does the USAF really do two full 360 degree turns, so you come back to the starting position twice? Does anybody have a reference for this? The verbal instructions seem to confuse 90 degrees of bank with 90 degrees of turn... unless the USAF also requires a 90 degree bank at the top of the climb? Link: http://avstop.com/ac/flighttrainghandbook/lazy8.html

Haven't had the opportunity to get to an airshow for a couple of years, and I thoroughly enjoyed this one! I spent a lot of time hanging around where the performing aircraft were parked so I could watch them start up. The T-33 surprised me with the awesome bass growl when it first lit; very different from any modern jet engines I've ever heard. I think the A-6M Zero was one of the biggest highlights of the show. Not many opportunities to see one of those flying! In the static displays, I loved the replica Wright Model A and want very much to learn more about that project. Who built it, where, when, using what documentation? Obviously that little modern engine isn't authentic... how about the rest of the plane? Is it airworthy, or only for ground display? Man, I loved the looks of that bird.

Options - Special - F-86F Uncheck the box, I think it's labeled landing seat adjustment.

I don't know. Never had the replays work for me at all, so I just stopped using them for anything.

Thank you very much, zaelu! Problem solved. :) I thought the issue magically fixed itself last update... I must've stumbled over that file and immediately forgotten about it, like a derp. :lol:

While I'm sorry people are having problems with this very fun module... I'm glad it's not just me. Thought I was going crazy and/or messed up something extremely obvious.

Just to add to the mystery, in hopes that if any other person ever experiences the same problem then maybe this little thread can help them figure it out... After today's update, once again I'm back to the default max FOV, and editing Views.lua does not have any apparent effect.