Oscar Juliet

If you check out our website and read our frontlines briefing you'll see how I structured the frequencies. They seem to work out for everyone. Might help your server out too if you borrow some frequency ideas.

The calculations from this mod and our spreadsheet at -7 are the same. So it is correct. +12 for Nevada which is on charts for the Nellis area gives almost accurate results. So this mod will not work for 2.1 calculations. NOTE: Using plus 12 on our spreadsheet and in high winds on Nevada we still will miss targets with guided weapons. If targeting a tank it will land next to it. This isn't noob error either. It happens with all of us. We don't know what the perfect laste calculation is on Nevada.

It is really simple. This is our server and we run it for people to enjoy. We don't have time to argue and will refuse to do so. Everything that is in writing is because of people who lack common decency and common sense. If you come under our radar and end up being kicked or banned there is a good reason for it. Myself and our staff will no longer indulge you on the forums.

Since you decided to take it here instead of coming to our discord I can assist you. I banned you, not Max. The reason you were banned is because you chose to blatantly ignore our briefing pictures, the first paragraph in our briefing, and the briefings on our website. When we kindly reminded you of the rules you wanted to argue you with us in chat while we're flying a 5 ship A10c mission. We have very relaxed rules and regardless of your perception you should read in full and ask questions on discord if necessary before jumping in. You were banned to make sure you didn't cause a problem on our server until you could read our briefings and join us in discord. Have a nice day.

Your support and addition to this thread is about what I would expect.

This mod works and is IC compatible but the calculations are WRONG for 2.1. It gives you wrong LASTE data It uses MagVar -7 which is great for 1.5. I've read we should use a +12 in Nevada but I have no idea. Either way it drastically changes the way LASTE is calculated. This mod can't be used on 2.1 effectively. https://docs.google.com/spreadsheets/d/1xYATEyeH3hHkkaDqcFj-__mZWIin5u2HEFdonp-0k_w/edit#gid=1491611486 This spreadsheet was imported from one that was given out on the forums.

You can drop units anywhere you wish and command them to attack targets. Best thing for transport pilots is to build hawk sites for air defence. Each a2g jet mission has a JTAC at it. Heli missions don't but if you drop a JTAC near a heli mission it will mark targets with smoke. There should be some obvious stuff like don't build on runways. Not sure if it would even let you. You're free to do as you please. Our briefing mentions what to do if you're a heli. Keep your lights on at the airbase at all times. Stay below 500 AGL or below is a good recommendation while near airbase. Cross runway only after stating intentions and verifying its clear. You don't need to Taxi but you do need to be very careful as a helicopter. Reckless flying will not be allowed near airbases. SRS radio is helpful too.

@lefty we will look into it. Should be available at any airbase. Pandion is recruiting.

Issue was with the latest DCS update. We've fixed the problem.

MP Issues -Player randomly explodes mid flight without any reason. -Player randomly is kicked from plane to spectator mode without reason. I would not have believed this for myself until an event on our 2.1 server. I was GCI spectating the entire event and making sure it was operating smoothly. I watched as on guy in an FC3 SU-27 exploded three times mid air without anything near him. He was not shot by air, not shot by ground, no other friendly planes or anything at all was near him. He just randomly blew up into tiny pieces. Another guy in an SU-25T was flying his plane and twice he was kicked to the spectator slot. As these problems were occurring many people said 'oh yeah i've had that happen before' as if it were a normal problem. I'm dumbfounded by how this can be a 'normal bug/problem'. Does anyone have any information on this? It seems to be completely random with different aircraft. I hope this will be taken seriously because it would annoy me beyond belief if it was happening to me.

Through the Inferno operates exclusively on spawned in missions. In both 1.5 and 2.1 they cause lag spikes. I'm glad to see this is an issue being taken seriously. We even had personally reported it at E3. We're also experiencing new lag spikes anytime a play loads into an aircraft on 2.1 only. They render the plane slow as the pilot but everyone feels a huge spike when a slot is taken. Our missions random generate missions that spawn. It doesn't seem to matter how many units are in a group. Small groups or large groups all seem to have the same lag effect. It doesn't matter if its ground without radar units, ground with radar units, air units. It all does it. Fixing this would make online play so much better for our servers.

Have a look at our 1.5 server. Perfect for beginners. All links in my signature.

Seems like it has been stated but if it is not clear always make a markpoint on a target you don't want to lose. Use area track vs point track when terrain is an issue of getting in the way.

^Solved Haha good news. Sometimes that happens. Silly things making ya think something is broke.

Default DCS escort task.

I use CH products and have since 2013. The only time I've had toe brakes not respond is if you set your profile up to combine the controllers. These are instructions i wrote to a friend who just bought CH and loves it. 1) Open CH control manager 2) Click the map wizard button. Its a white paper with a lightning bolt 3) Choose your fighterstick, pro throttle, and pro pedals and hit okaky 4) Do you want to combine controllers? hit no 5) Do you want to include CMS capability? hit no 6) Press Finish 7) now you will see the controls show up on the screen now to save it 8) hit the blue save floppy disc and call it MASTER MAP 9) click the button called direct mode. It looks like a blue rectangle with 3 lines coming from it. 10) hit the calibrate button and now you should see all three devices and their names 11) calibrate each device and follow the on screen prompts 12) save profile again Each time you restart windows you need to hit 1) load profile 2) load MASTER MAP 3) hit the direct mode button If you don't hit direct mode windows sees your controllers as device 1, 2 and 3. Instead of by the actual name. DCS will read it each way as well. So you want to make sure its in direct mode before setting up controlls in DCS. I recommend programming all controls inside DCS

Thank you for the response

I don't know if yall know but we host this online. Modified heavily with many upgrades on 1.5 and 2.1.

I tried to google and search this to find a solution before this post. I can't get the escort task to work properly. The F15c escort starts at 18 thousand feet and slowly loses altitude until one of them hits the ground. Then the other skims the ground following the tanker around. I want them to follow up at the same altitude. I need help figuring out if its a bug or if i need to change some parameters around. Had an image up but my hosting provider is not allowing it to work here.

MWS is reliable against all other threats including some non threats like TOW missile launches on the ground. So for it not to be reliable against one of these I would like to find out why? We placed many of these in the desert on a mission in 2.1. Only one launch warning out of several last night. It is very hit and miss. ED will need to address it as a bug or provide documentation as to why it is not a bug.

I do believe certain people are not capable of reading posts. Of course my MWS is on. The video shows there is some sort of problem. I know this isn't the only way to watch Igla threats as I'm not only a lead with a decent group but I explained how we currently find the threats. It is a bug that needs to be addressed and has been reported on multiple occasions. The purpose of this thread was to find out if it could be fixed via mod.

Welcome to the server and we're glad you're enjoying it. Make sure to join us on discord. Admins are always available to handle issues. We ban many idiots each day but overall things go as they should. We have big plans in the works for 2.1. A persistent mission in the NW region while maintaining our normal TTI functions that 1.5 is so popular for around Vegas.

http://i403.photobucket.com/albums/pp113/HolyOrangeJuice/2321312.png This happens on an up to date DCS 2.1 install. Repaired, Cleaned, no mods, no deferred shading. Game works fine without the program but as soon as i turn it on this happens.

What you are showing in this video does not happen for myself or any of my pilot's who fly with me. We fly a modified version of Bactria that is available on the ED site. There are many Igla's on that mission buried in the woods so we often get fired upon. Unless another pilot is looking for smoke we never have an indication of a launch. No missile warnings ever. I've seen someone flying by an area just like you are, they get shot and smacked out of the sky because they never got the warning. This controlled test seems to work. It doesn't for us in a practical mission. Something is breaking it or causing it not to work properly. I wish it wouldn't be overlooked. Even in the control sometimes it worked and sometimes it didn't. Everything else works for launch warnings but not this.

Latest beta build fixed my problems in 1.5 but I can not make this work in 2.1. I had a bunch of window exports open that couldn't be used and some were displaying nothing but blackness. I had green text and other distorted exports on the screen as well. I even tried with deferred shading off but my game would just crash.