ENO

Eh guys. I'm trying to get some stuff worked out with "removing" the pilot from the above scenario- Ragnarda was nice enough to point me to the script- and I've been trying to put it to use from the hoggit wiki. function Object.destroy(Object self) is the proper script and 'vega1 downed pilot #1' is the name of the pilot "object." I've tried putting the name in (Object self)'s place... and in various other places... seems it isn't going to be that easy. A quick hand would be appreciated...

That's not a bad point actually.

Servers can see how much data they send to each player and weigh it against how much upload bandwidth they have. They have a good idea how many people they can host and keep performance up.

http://forums.eagle.ru/showthread.php?t=108476 Probably as close as you're going to get.

Ooooooooooh. Then no- I don't think that's available as cich said.

There are some pretty casual groups of enthusiasts out there who are quite helpful to anyone willing to put in as much work to help themselves as they expect from other people. The firehouse / hollo pointe servers definitely fit that description- but there are many others I'm sure you've read about.

Have you tried running it with no input devices at all? You may also need to rename your input folder in user / saved games / dcs / config (as a backup) and then run the game again. The game will rebuild that folder... see if it helps.

By stick commands I originally figured he meant stick inputs but after reading it a couple times I saw he was talking button presses on the stick and throttle. Only way to do that is going to be in the control panel...

OP: Once you get your registration sorted out (that shouldn't take any time at all) the world of multiplayer can be a little daunting. I posted this a bit ago for someone else who was making their way into the MP environment and figured it may be helpful again: Typical experience you might expect from the firehouse server as an example. Log into SimHQs TS3 (free reg required) and head down to the SimHQ Firehouse room- choosing red or blue. There may be guys in there... there may not be. Get any track IR / view equipment started up. Log into MP server lobby and go to "Eno's Firehouse." Once you're in there, you're put in the "spectators" section where you will see an array of available aircraft to choose from. Remember- there are some very similar aircraft available now including the A10A and C, SU25 and SU25T... etc. Make sure you choose an aircraft slot that suits the modules you own. You won't be able to read the "red" or "blue" briefing until you choose your slot- but you will be able to see the "Situation." READ THE BRIEFING! Most of them can appear long now that we have so many different mission capable aircraft onboard. I can't speak for others but I split the briefing up on a "per aircraft type" basis to keep things reasonable. Good to read the "Situation" so you can begin to get an understanding as to the "feel" of the mission. Read your particular aircraft type... and if you're interested in what the others are doing- read theirs. It makes a bit more sense of things later on. You can always refer to it throughout the mission while flying... but sometimes it helps to figure out what you want to bring with you if the default loadout is either empty or not suitable to your skills / expertise / task. If there is anyone in there, undoubtedly you'll have started to have a conversation about where the mission is at and what the folks are working on. It helps to mention that you're new to MP... it allows the guys to anticipate questions and gives them an idea what your abilities are for tasks later on. It helps to have a normal Warthog HOTAS but it is by no means a requirement. Because of the wide variety of control interfaces available, it IS helpful to know your equivalent inputs. For example: You ask "How do I set SPI on the TGP?" I would answer "It'll be the equivalent of TMS up long." Some guys have the key lists in front of them but it's much, much easier just to give you the actual control interface. We have cold and warm starts available so if you're not feeling up to a cold start, often we have warm pits to get into (if they're not already occupied). Go through your startup- whatever it is- and check your loadout. Doesn't hurt to ask the guys if there is any particular weapon type you should be bringing with you to help them out... Some servers are more regimented with their radio procedure with ATC and some guys enhance their sense of emersion by being quite formal with their TS3 speak. We're "Semi-formal," in that courtesy notification of approach or runway occupation. "I'm taking the active 08 at Kutaisi" or "Inbound long / short (no prescribed distance necessarily) 08 Kutaisi." These are examples only- as much as to say that we talk a little more conversationally. Some guys go in there and are REALLY formal about it- but they don't hold anyone to a standard. That's how THEY do it- and generally they are expected to acknowledge that not everyone on an open server is going to hold themselves to the same standard. ATC radio inputs are a bit clunky but where they help out is in defining what the active runway is. SOME servers are VERY strict about taking the active- but if the active is on the other side of the map and you're in there by yourself or with 2 or 3 other guys on TS3 and nobody declares that they're inbound or in the area... I won't tell if you don't! Taxiway takeoffs, however, are VERBOTTEN and a VERY bad habit to get into. Once you're in the air, again... in our particular instance we're not formal but we do communicate well as a group. Generally we've found that visitors merge well with the regulars and get into the groove quickly just because the comms are more conversational. Tell people what you're doing so they can look at their TAD and make a mental note of where you are and figure out if what you're doing is going to affect them. If they have a question or a conflict... they'll tell you... and all is hunkie dorie. When you're running low on gas then you just say so... if you're out of ammo then tell the guys... Quite often guys still like the formation flying aspect and will join up with you if they're close to being out of ammo or already on their way back. We don't fly really close (yes, it can still glitch a bit) but some attention to detail is observed. If you're wondering how to line up properly- just ask... typically whatever your distance you line up the outside edge of your pertinent side rearview mirror with his wingtip and the ejection seat triangle... whatever your distance if you adhere to that you're in the proper orientation. Landing- again... it helps to "sign in" with the radio ATC because if there are other people (not on TS3) at the airbase you're approaching they won't be cleared to access the runway... It also helps to just communicate it out loud to those on TS3 as they may be operating on another channel. If you think you're going to cream in- try to stick one side of the runway so it doesn't block others from taking off or landing. Typically your wreckage disappears if it's so bad that your plane explodes and you get in another plane... but if you need to repair your aircraft (takes 170 seconds plus actual repair time)- sticking to the side helps the others around you (if possible). It's not hard for ANYONE to understand if you've attempted an approach on manual reversion on one engine and missing half (or all ) of your rudder surfaces that you end up on a collapsed gear in the middle of the runway... We'll get it ;) Anyway- that's a bit of a description of what you might expect. Sorry if it's a little longer than I expected!

So to be clear- you're just looking for a way to see your joystick inputs and if possible your keyboard inputs? One way is through the windows control panel into devices and then device properties... you can see the controller input screen there. There's another command that will show joystick and pedal inputs but I can't for the life of me remember that keystroke. CTRL+ (something)... anyone?

Yes again I said its a stretch- your issue isn't ping related but that service- if on your comp- may be impacting a different way. I tried to connect and got a Can not connect also.

http://forums.eagle.ru/showthread.php?t=109510&highlight=ethernet+issue&page=2 Around post 14 they begin discussing the ethernet "service" I was talking about. I'm pretty sure this was what I was thinking about- it sounds like a stretch but it's worth a look.

I don't know that it'll matter- but I'd be interested in seeing what happens. Go in and change it to "false." I'll keep my eye open for that ethernet problem.

Yes - the servers are still encouraged to use LAN. And 100/100... Drool.

Very likely yes. Considered a mild overclock on your CPU? What are your thoughts on moving towards an SSD? What's your budget?

http://forums.eagle.ru/showthread.php?t=121095 Not to mention the this one here. The fight continues.

Are your drives connected via the same type of port controller or across a range of controllers? Have you tried moving your full install into the standard location to see if that works? Then you can muck about with a custom setup.

In the past I've read that some if these issues relate to some sort of Ethernet driver issues. I'm going to try to hunt that one down. Also rongor- is your network.cfg set to pause on empty?

Sorry rongor I get it and its frustrating over on this end too knowing that it should be THAT easy to set up a server. I hope we can figure this out.

Yes, you have some good points I hadn't considered. You said you reinstalled with the STEAM version. Just for excrement and chortles have you considered dumping that install and trying the DCS / ED version and using your STEAM key? And just to confirm- you're not running ANY other modification? Just a straight up DCSW install plus whatever you've done in here?

Actually to add to that it's also pretty well accepted that if there is substantial ground action or CA involvement 2048 should be the ceiling of your connection. Depends on what servers you tend to join- but if they're more adversarial / A2A then 1024 should be fine. More A2G related missions should be 2048. It does make a difference in terms of the load the servers can handle and I think the general message out there is "don't just keep it on LAN because that's the way it's always been and it's fine." Things change and as the platform changes, we all need to make adjustments. The ONLY time I've found (personally) that 1024 didn't work well for me was when I was actually hooked up via LAN (the server comp sits 2 feet away from my client comp). I experienced substantial warping. However, with that being said now that I'm typing this the mission being run at the time (the 127 stress test mission) was running enormous amounts of AI in the air and on the ground and that may have been contributing. Worth some thought either way.

Fricken amazes me how you guys can do that.

While using the editor the other day I came to realize how much I miss "CONTROL" and "SHIFT" + LEFT CLICK functions to be able to select groups of units or individual units throughout a group. For example with control, being able to pick out several individual units within a group to assign them to skill levels or headings (etc), or with shift being able to select a block of units (starting from whatever point. Similar function as within windows I guess is what I think would be "nice."

This sounds like a problem I had before after accidentally using "prepare mission." You'll need to change the miz file into a .zip file (or .rar .7zip whatever)... then go into the file and delete the warehouse folder. Then go back and change the extension to .miz again. The airbase affiliations will have changed back to stock so you'll need to go back and change those back to the way you like them. Also, you'll need to ensure that you have (known / common) extensions visible in your windows control panel otherwise you won't be able to properly convert the file between miz and your program of choice. (Many use 7zip configured to open .miz to avoid having to convert).

Yes. Sufficiently for it to get your ip but maybe not to stream the data necessary to hold it. At least that's what I'm seeing. I thought the tracking was from crews server to the master... Didn't realize it was just to his own. Thanks though crew.