mkosmo

Once you start running your server, you'll realize that thread/core count does not matter. Like the rest of the game, the server will consume a core and that'll be the end of it. The thing chews RAM - so that'll be your contention point. My free-flight missions chew 8-10GB of RAM per instance by themselves, and they don't even have a high unit count.

Citation required. When checking my missions for 2.7 compatibility, I diffed them after an open/save in ME. The only "changes" were some ordering, but no functional changes to the Lua structures themselves.

Maybe if they're validated... but if somebody were to texture some invisible skins, it'd create a false competitive advantage. I understand why these textures are part of the IC.

No, not really. If you need to yaw right, add right pressure. If you need to yaw left, add left pressure. The problem with the sim is that you lack the feedback, both in the pedal and your body. Some people make some of the stick and rudder of flying sound a lot harder than it really is.

Templating: The ability to have predefined groups that can be quickly placed in a MIZ, whether it be a preconfigured flight or ground units. Not having to recreate the same things over and over, especially with all of the possible options to have to change (livery, radio, loads, or even routes, times, etc) would be fantastic.

What'd be nice is to be able to set sea conditions so we can get some deck movement!

In my other thread, ED reported that the webui not responding was related to a compiler issue and systems without AES-NI. Once I had my host move my VM to a machine that would expose AES-NI to me, my webui started working again.

I can confirm that it started working again once AES-NI was exposed to my guest.

Fantastic news! My hosting provider is migrating me to a newer host with the intent of exposing AES-NI to my guest. Assuming the migration works, I'll report back.

Interesting. I had no idea I was missing AES-NI on this box until I went to go check. Since my box is a VM hosted on a E5-2697 v3, which supports AES-NI, I just assumed it did. Coreinfo has since demonstrated that it's not enabled. Time to go put a ticket in with my host. If AES-NI is then enabled, will this resolve itself?

Watch the ball to coordinate. An aileron roll doesn't require opposite rudder at the 90, as that would take you out of coordination. There should be some deflection in the direction of the aileron travel.

I take it you're not a shooter.

ED mentioned they could replicate it internally in my thread: https://forums.eagle.ru/showpost.php?p=4053917&postcount=8

Considering that the low-res mods I've seen actually replace existing files, I doubt it's quite that easy.

Same symptoms. Didn't start until 0830z. Just restarted it and it seems to be working, though. Server is back in list.

Are they running the correct version?

Sounds like it's not squelching. If you turn the com1/com2 volume knobs all the way down, it goes away.

There are lots of ways to log. FAA civil is from the time the aircraft moves under its own power for the purposes of flight to shutdown... Some entities log wheels up to wheels down. There are even some that log wheels up to shutdown (which seems to be what they're trying to emulate here). A tenth here or there being wrong is negligible and shouldn't be something to be up in arms about.

Glad to hear it! If you can keep us in the loop as to the process, we'd appreciate it!

As expected (no change to my hosts file):

Yeah, I just want to bring more attention to it. I'm hoping ED will take me up on the offer to explore an affected system, or take notice to the certificate issue and provide some guidance on how we can isolate and locally work to remedy the issue.

Perfect -- Same symptoms from both a "supported" platform and not. Hopefully we can get something more from ED.

That's not how networking works. Firstly, you're making the assumption that the modem is a "router" or NAT gateway. If it isn't, it's probably not an issue. If it is, so be it. While double NAT is ugly in nearly every case, it's not insurmountable, and the local application (particularly network applications like this) will be generally oblivious to it if you have appropriately configured both NAT devices. The key is to configure both NAT devices. On the other hand, there's not even enough information here to know if the user is actually being assigned a globally routed address on the outside of his router. As is becoming more common in these included services, if he's only being issued an RFC1918 address, it'd have to be coordinated with his upstream.

Since the last thread in here was closed some time back, I wanted to follow up and see if we could find some kind of resolution. Yes, I'm running Windows Server 2016 R2, but let's not hide behind the "unsupported OS" claim -- this worked until earlier this year. Windows 10 and Server 2016 R2 are similar enough that nothing unusual will be going on here. When the client makes a request to the 8088 service on the box, it's getting back a "422 Unprocessable Entity" from the service, so it's connecting just fine. I also see the same response come through the website, but it's passed back as the response payload of a request that otherwise is indicating a 200. Local: https://i.imgur.com/WTIc86y.png Via the website: https://i.imgur.com/YMJvLiG.png Possibly relevant line in the logs: Where may I be able to find that certificate mentioned in the log line? Inspection of the certificate may assist some local troubleshooting. I could not find any files in the install or Saved Games folder that used common pkcs7 extensions. Since I saw on the last thread that local testers were unable to reproduce, if ED is so inclined, I'm willing to set up a call and sharing session such that the team can get their hands on the system and work with it in any way that may assist in diagnostics and resolution of this issue. If you'd like to set anything up, please PM me and we can go from there.

How to avoid stalls? Don't pull back so hard. Don't go so slow. At the end of the day, do not exceed the critical angle of attack. How to avoid spins? Don't stall in the first place.