Smoky

I reinstalled, repatched, repaired, deleted all dcs folders, rebooted many times, tried logging in using my client login on my server machine, made sure someone didnt change my router settings (actually not possible as I am the only one who knows the admin pw).. And so on.

My problem continues. Nothing has changed on my router before or after the 1.2.5 patch. The only thing that changed on my system during the time when my server began reporting the can't connect to master error is the 1.2.5 patch. I didn't even install any windows updates. The only thing installed on this server machine is DCS World and Windows. Stumped.

There are several log files in that dir. Which one is of interest?

Since the other thread got hijacked and then closed before a resolution could be suggested I thought I'd start another thread. I have two machines. One is my client, the other my server. I've been running the server without issues for months until last week's 1.2.5 patch. Now my server only gets the message "Can't connect to Master". I've reinstalled and tried many of the suggestions on the forums. My client machine continues to connect just fine. Did something change about 1.2.5? Is the SU-25 no longer included as a freebie in 1.2.5 requiring that I buy a module license for my multiplayer server? Previously this module was enabled and though it is still available from Instant Action the module is now marked with a "$" symbol. Any suggestions? Thanks

Anyone?

Hi folks Ever since the most recent patch my multiplayer server gets the cant's connect to master error. Tried everything so far. Even reinstalled. Is there an issue with the patch? I'm not seeing any posts. I can ping the master server just fine. No matter what login I try it just gives the cant connect error. I have looked for a temp folder to clear as instructed but none exists except for a texture folder. I've reinstalled and deleted all DCS folders before installing again. I reboot between installs. Everything is patching fine. Single player loads into instant action fine. Everything was working 100% for several months of hosting prior to the latest patch installing. Multiplayer on my other client machine works fine after the patch. What else can I try? Thanks!

One question though... If nothing major is wrong and only small bug fixes are being addressed then why release a major patch? Ideally everything would stay compatible for optional minor bug fix patches. Then major patches require everyone to sync. That way all camps are satisfied. It just doesnt make sense to patch so often if nothing is wrong with the majority of installs.

I LOVE DCS. It's the simulator I've been dreaming of since I was a kid wishing that FS 1 and Jet were more than they could ever be. But.... There are too many updates. Too many patches. I'm sure a hundred people will be lining up to tell me why what I'm saying is wrong or sacrilegious. Nevertheless I feel compelled. I know I'm just one dumb customer with an opinion...but from my seat we are patching too much. Please consider the impact of a patch: -long download wait times interfere with gaming plans (for those of us with kids, this is a big deal because it might be another week again before I can find time to dedicate as this sim isn't a sit-in-and-go affair). -servers must be refreshed. Last night due to an "invalid serial key" error I had to reinstall all of the DCS software on my server and reupdate before it took. This buggy process took an hour and a half before it was sorted out. So now I have to anticipate this overhead as well. -mods must be refreshed. Both clients and creators alike have their world turned upside down by most patches. Not saying you have to care about that on the backend code (though it would be nice to support your supporting modders), but it would be nice to consider this point. Would a quarterly patch cycle, yielding four updates a year, not be more feasible for both development team pace and iteration load management and for client? Or least SOME sort of predictable schedule, eg "DCS will patch the first of every month. If there is no patch on the first then the next opportunity will be the following month." Again, I'm not trying to be the guy griping about the little things. I actually think this is a big thing. If my company put out patches at this rate we would honestly be out of business in a year because it costs our partners time to patch and update their networks accordingly. They would be more than displeased. I'm also trying to bring what I think is a reasonable solution to the table, rather than just griping. I would be very interested to hear other thoughts or proposals on how to mitigate and maximize the return on effort that the DCS team is putting into this wonderful sim. Thanks for your time

A lot of the JTAC-specific tutorials forget to explain that you need to know more than just how to communicate with JTAC. You have to know and understand: -how to input data into the CDU and/or UFC + MFD CDU repeater -how to read and use the TAD to find, designate, and share targets -how to use your weapons systems to tie the above together to make a kill Search for youtube videos that cover these other topics in-depth to get the most complete understanding of how the systems all work together.

Try uninstalling and reinstalling then report back.

Giving Simmod a try but I can't get it to generate the config.lua the instructions says will be generated after launching a mp session. Since that's the first big step I'm a little stumped. I unzipped the scripts folder into the Saved Games/DCS folder. I ran multiplayer, launched a server, then exited. But no config.lua file. Am I doing something wrong? Simmod seems to be installed correctly as I am able to execute simmmod -admin commands. I'll keep messing with it. Though I'm sure default settings are fine. I'm only after the auto-pause/unpause feature mostly.

Thanks to your handiwork my friend!

Thx! Thats just an led bar to add a little character to my beast.

I will look into it. Is it relatively version agnostic?

A little video I made last night demo'ing the aviation setup of my simpit (3 ELO touch panels, 1 AE1000 projector, and a dash of Helios magic). Thanks to ED for making such an incredible sim.

So far so good! I haven't been able to stay logged onto my server this long before. Thanks again for your help!

I'd seen FubarBundy's post before. Your post was more helpful. Got me thinking about what I was trying to do. So I made sure both client and host were on the same vlan (previously separated as an experiment) and the server popped up instantly. Now I will try to see how long I can stay connected this way. Hopefully this is the solution. I was too mired in the other details to see this. Thanks for getting me back on course.

Editing because my reply made no sense. So how do I connect "via LAN" ? I have the server speed set to "LAN" I have the client speed set to "LAN" And I am connecting to the server using Connect by IP. When I click "Source" = LAN on the server list the resulting table is empty.

So I just changed a bunch of stuff...ports on diff vlans, explicit any/any firewall rules for the 10308 port service for udp/tcp, server on static ip, this and that... still "Connection Interrupted". Only happens to me. Only I cannot see my server in the server list. Everything is peachy for others. If other folks don't mind giving it a shot I'd like to see if anyone else experiences the Connection Interrupted" error message and consequent disconnect. The server name is "Eagles" Or if you cannot see it, that would be helpful to know as well. Thanks

Not sure what else I could tweak on this router beyond what I've already tweaked. Truth is an old router can really put the hurt on things. I didn't realize it until a recent install of Windows 8 would not connect to any MS servers for Windows Updates. Firmware flash and voila, it worked again. Maybe not the same issue here, but a new router will be a good place to start I think since I feel like I have all the other bases covered. I have to believe that since others can get in and play for hours that there is something going on with the server and host being on the same router, same subnet, etc. Maybe. Not sure what else to focus on.

I have an rv082 and its about 6 years old with no further driver support since last year. I have a new 10 port i ordered last week on the way wednesday. I hope that solves it.

Hi folks I've hit a stumper here. As I have understood all the trainings, write-ups, wikis, how-to's, etc, I have everything set up as it should be. What is happening is that everyone outside of my network is able to connect to my DCS World multiplayer server. However when *I* connect I am only ably to stay logged on for a few minutes before I get the dreaded "Connection interrupted" error. So I've created a server that everyone can use except me!! :pilotfly: What could this be? I have DCS World and DCS Huey installed on a separate machine which is running Win 7. That is all that is installed on this machine besides the necessary drivers. I am not using any fancy server management. I have ports open correctly (clearly, since outside users can access just fine). My host and client are on the same router, different IP. I have a unique DCS login for the server and my own DCS login for the client. I cannot see my server on the server list. But everyone else outside of my network CAN see it. Should I try putting the server port on it's on VLAN? Would that matter? What else could I try? My Client machine is a Win 8 machine It Connects to my server, but can't stay connected. Gets "Connection interrupted" error each time. My Client cannot see the server and is forced to "connect by IP" My Client machine can connect to any other accessible DCS server in the server list and I stay connected just fine. I ONLY get the Connection Interrupted error when I try to connect to my own server and ONLY I get the message. Works great for everyone else. Help! Thanks

Just want to thank the Helios crew and the DCS crew for developing such fine products that work together so excellently. I'm so happy to see that after all of these patches my gauges, touch monitors, and views all still work perfectly. Thank you teams!!! This is the sign of top-notch products. PS: Eagle Dynamics please bring Helios on board officially. That would be incredible.

Search for: Helios There are other options too. My pit is fully clickable as you describe using 3 touch panels (fore, and L/R panels, + external view on projector) via the Helios software. Video coming soon.

Nope, I really just want to get rid of the cockpit interior as much as possible. I've come across threads where people say they have "tubbed" the cockpit display. But there is no explanation or follow-up to my queries on "how", so maybe they were just stories and not real accomplishments since it seems so far like I'm the first to ask this question. I might give this a try in the cockpit builder's forum. I just thought you guys would know the ins-and-outs of A10 better. Or I thought someone from DCS might chime-in. We have a of pit-builders here so it would make sense to be able to disable the cockpit interior. Or am I the only one who thinks that?