I absolutely know what I'm talking about but the problem is that they hired someone like me to do the program. (A non programmer or a novice one).
I've been playing on-line games for a while now (around 90')and never experienced a continuing problem that wasn't fixed in minimum time.

There are games that can have over a hundred players without a crash. In the last few months I've been in servers with 3 people and experienced it.

I love the title but am finding myself playing other things because I don't want to waste time setting up only to have the server or game fold.
People that tell how great things are don't help anything.
Only good will come out of getting the most basic thing corrected first before proceeding. It will make everyone happier.

Just because you can play other games and they work this way or that way, doesn't mean that a programs with problems has an incompetent programmer. These are quite complex pieces of software; it's easy enough to break things without touching the network code.

The problem isn't the network dev's creds, they have quite good ones. The problem is your attempt, as a novice/non-programmer, to speak to someone else's skills when you don't have a clue of what it is you're actually talking about.

Contrast this with saying that there are problems with DCS MP; no one will deny that.

The instability does beat down on my enthusiasm as well- mostly because it's my server crashing on everyone

You bet; it's beating down everyone's enthusiasm, including the devs.

My main issue ghost is just that I don't know how far to go on my problem solving measures if the problems are in fact inherent with the software. If its something I can correct I want to correct it but it's very difficult to nail down whether it was a program crash (there was a problem with dcs.exe the program will now close) or a server problem (connection timed out or interrupted). Looking at those two things it would seem obvious- but are all the errors with dcs.exe the software- or are some caused by network issues. Who is to know?

Crew and I do a pretty decent job keeping things running- but some assurances that they know what the issue is and are working on it would be nice.

Eno, regardless of what happened to the internet connection, the DCS executable should fail gracefully - ie. it should not crash/close/whatever all on its own. It should just fail to serve and tell you so. Same thing with an interrupted connection - if you have a way of checking that your network is working just fine (ie. connection interrupted while your RDP'ing or using Teamviewer, and obviously the network is working fine).

The only thing to do is to report the crashes and provide the logs. These are bugs that need fixing. I can't discuss internal matters, but these problems are known and beeing looked into.

GG, please take a few minutes and tell us how you think we should report issues?

Create a post on DCS Forums and keep adding new logs to it? What logs, exactly?


We will do whatever we can to help to resolve this.


WC

Yes, post them in the DCS forums; for example, in DCS WOrld/Bugs forum, and title it 'crash logs' or add logs to another thread that might be similar. The testers (and ED's internal lead tester) tend to come around and collect these and enter them into a bug database. Don't expect too much feedback, but we definitely look at these these things.

If I find out that crash bugs were fixed, I will let you know.

See this: http://forums.eagle.ru/showthread.php?t=88164

Thanks for the link, EtherealN,

But it makes me wonder if v1.1.1.1 incidents are even in focus now that DCS World is out? I'd bet not.

But for DCSW hosting this will be a good guide on reporting.

WC