TynMahn

For some reason, it doesn't seem like the server is showing up on the DCS Multiplayer Normandy list in game

As far as I've seen over the last couple of months it's been back on-line, it is always up and running. It is a really neat concept.

I see you online line right now and all those gains that they made yesterday have been wiped out ....

Very relevant and helpful information. More information in detail would be appreciated as well. Examples of situations and appropriate responses; for example. Thanks for this.

Got "SLMOD INFO: [...] autokicked back to spectator" Not sure what this is or why it happened

1. I completely understand and appreciate your approach and feelings on this. I figured it was conscious and I figured it was done for pretty much the reasons you expressed. I only brought it up because, playing online with other real people, it is kind of nice to know who you were pitted against after the fact. Maybe an "after action" type record could be accessed like on the stats page that you are working on. Where someone could go after they've played to see who they were up against in that one hard fought engagement or whatever.

Is it possible for the server administrator to allow for a "player list" that show who is on the channel and who is transmitting?

I'd like to offer the following suggestion: Would it be considered to put in the server messages like they have In LFDM? The server has a message telling who shot who down when it happens, it also gives messages when allied targets are being engaged. Not having these messages may be a server admin decision and I may be in the minority but I really miss these messages whenever I fly on SoW. It is nice to know who just handed it to you and encourages a more "communal" type gaming feeling.

So, I think I pushed a button or something and caused the following to appear on my screen. In the upper left "Main" is displayed and in the upper right "Static1" is displayed. Can anybody tell me what I did to cause this and how do I make it go away? Thanks.

Was finally able to get back online (unfortunately, I started out as a steam user and have so much money invested, I'm stuck there) and did some flying on SoW. I noticed a couple of things 1. Static mustangs at Beuzeville were not sitting on the ground 2. I don't know if this is a setting I have to adjust, a limitation in DCS or a server settings but, I was attacking the railyards at Carentan and most of the ground objects (trucks, train cars, etc) would not render until I was almost on them...makes target acquisition and lining up for an attack run even more challenging guessing where you are going to shoot until the last minute when the object pops into existence I don't know about other people and I don't know how I'll feel in the long run but, just starting out on this server, I like the semi-single playability aspect vibe I get from it. I feel like it's kind of a merger of sp/mp … I think it's pretty cool, so far.

I've been flying LFDM and I checked out SoW because they are Normandy with WWII assets I hope, when burning skies come back, they consider switching

The QMB in this sim is crazy crappy. It's too bad because it is one of the few areas that, if given proper love, would go a long way to making the game more approachable to new users and help boost the base

Yes The QMB thingy in this Sim needs some serious love

Yeah, not working for me for some reason

I too have encountered this problem, and recently. I have, on at least 3 occasions, ran into long standing mostly minor but, mostly really frustrating issues, like this, that have been around in this sim for months, even years before they are addressed, if ever. The other two issues that I can think of off of the top of my head right now persisted for YEARS before they were finally resolved. Not only did they persist for years, they were never even really acknowledged by the developer. Nothing was said, by the developer, about them knowing about and looking into the problem and no help or temporary solution was offered to alleviate the enjoyment killing experience caused by the issue. It seems, from the fact that this post has languished with no reply since November 2018, (a full year prior to my encountering the same issue) that this is yet another example.