Slazi

"they can use cannon only" Ka-50 is top. U1-H1 is unlikly to kill the Ka-50 as it lacks punch. The Mi-8 can be armed with a 23mm cannon, giving it a better shot, but still very unlikely. U1-H1 vs Mi-8 - Over range, the Mi-8 might be able to win. Again, the 23mm has good range and power. One or two hits is enough to stop the huey. Closer in, the huey with its special forces gunners will win.

No. They'll release information when they are ready.

Yup, one step at a time. But I still really think infantry should be able to 'occupy' a building. This would be great for ambushing armour and helos.

Soldiers need to do... something. Right now they are horrible. They need to use buildings and cover. Not just stand out in the open.

Thank you so much towsim. I'm going to keep looking at it and see if I can come up with appropriate modifiers for different areas of the grid. I doubt I'll be as accurate as I'd like, but I'm sure I can make some improvements to the results I'm getting. Thanks again.

Great info, towsim. Where did you get this all from? Was this discussed in a previous thread? Thanks a lot for the reply. It gives me a lot to look at tomorrow.

Possibly so. I'm still researching. Another interesting point, if you open up the map and turn off everything except the geographical grid, you will notice that the lines do NOT match up with the reference points given. If you zoom in and place your mouse cursor over the grid cross, it will not match where the lat and lon lines should match. Go to 46 0'8N 37 59'45E and you will see that is where the lines cross. Not 40 0'00N 38 0'00E. The lines cross 1339 feet at 305 degrees away. Perhaps this is a clue?

This is the interesting point. The 6 degrees is probably the magnetic deviation. This would make sense. A -4.4 degree error cannot be explained by that. There is of course, a chance that I'm messing all this up. If so, I'd be happy to be corrected for !SCIENCE! EDIT: I should also note that some of these destination points are off-map.

Thanks for the post Flagrum. Magnetic deviation is indeed one factor to think about. The first 6 degrees off could well be explained by magnetic deviation. However, the -4.4 and 9.2 degrees off definitely can't. Looking at that map, we are at between a +4 to +8 degree range (if I'm reading it right).

How do I manually calculate the angle and distances between airbases from the DCS world map? I'm really interested in plotting my own waypoints and flight path before I set foot in a DCS mission. I've been a huge fan of the Mi-8 since the Belsimtek module converted me, so I don't have any advanced navigation equipment on board. Ideally, I'd like accurate data, not estimates. I have a few questions that need to be answered to figure this out: How are bearings calculated on the DCS map? Magnetic? True? Other? If magnetic, what data is used for magnetic declination? How are distances calculated? Via Great Circle or Rhumb lines? I've looked into this a bit myself, but I really am just learning all this right now. Lets use Kobuleti to Guudauta as an example: Kobuleti 41 55 47.82N 41 51 48.54E Guudauta 43 6 51.36N 40 34 11.22E We can use haversine with great-circle navigation or Rhumb lines to calculate distances and angles. Both have their merits. It should be noted that they both use a spherical model of the earth, not an elliptical one. This would explain a slight inconsistency between results, but nothing like the inaccuracies we experience. We can compare this to the results we get in-game using the mission editor or F10 map (I used mission editor as it reported more accurate figures) and the data from the Ka-50 navigation suite: Haversine great-circle: Distance: 169.1km Initial bearing: 321°35′54″ Rhumb: Distance: 169.1km Bearing: 321°09′51″ In-game Distance: 91.777nm = 169.97km (Initial?) bearing: 315° Ka-50: Distance: 169.99km (Initial?) bearing: 315° The in-game results are quite different from the real-world formulas. The Ka-50 system seems to match up correctly to the f10 or mission editor view. So I use that for further tests. It seems we're basically looking at a 6 degree inaccuracy here, and a slight difference in distance. 6 degrees is significant. Very significant. Now, if it was constantly a 6 degree difference, it wouldn't be a problem. We could compensate. But, it's not. Let's have a look at some other extreme examples: From: 47 40 17N 45 16 4E 1000km 90° from this point Results: In game: 45 35 29N 57 39 19E Real-world: 46 54 13N 58 29 38E (Great-circle) Difference: 1 18 44N 0 50 19E (Great-circle) Difference: Great-circle: 27.44km 9.18° Rhumb: 26.43km 13.74° From: 48 7 46N 27 7 2E 1000km 270° from this point Results: In game: 46 42 19 N 14 10 4E Real-world: 47 20 58N 13 46 40E (Great-circle) Difference: 0 38 39N -0 -23 -24E (Great-circle) Difference: Great-circle: 14.12km -4.42° Rhumb 12.98km -9.23° I'm sure there are plenty of other examples that could show how far out this gets. But I think these are enough to show what I'm getting at. So, I'm guessing it would be possible to work out a formula to discover how much the angles and distances are out at each point, but I think that'd take a long time. Has anyone already done this? Is there any public information available? Thanks for reading.

Bios update for your mainboard may be another consideration

Hi everyone. I'm going to cancle this event as I haven't had much interested. I also lost my windows install on Thursday, so I'm still in the process of getting everything back to normal. Sorry for those who intended to join. I'll re-arrange this for another time.

You'll have to wait and find out :)

Yeah, sorry about my timezone. I could probably do from UTC 2:00 + on a Saturday if enough people were interested in that time.

As posted in the Mi-8 steam group: http://steamcommunity.com/groups/DCSMi-8#announcements Event: Duelling 8's My next planned event is something of a crazy one. Mi-8 vs. Mi-8 in a fight to the death. I plan to have varying load-outs for the different rounds. Fights will take place in a preset arena. This event is for Mi-8s. However, other helicopters may have a small role to play in some of the activities. Final details will be released as the event unfolds. This is event is flexible, so you can join at any time. You must have TS3 to participate and the lastest non-beta version of DCS World to join. Spectator slots will be made available for those interested. The event includes: Mi-8s fighting Other helicopters being used for sport Explosions! Mayhem Fun Flexibility If you're interested, please post your UTC availability below or in the steam group. Aiming for between 10:00 – 16:00 UTC on Friday, Saturday, or Sunday. Hope to see you there.

Perfect! Thank you so much! :pilotfly:

Lino, Great work! I have a question: I already have the airport information, but could I ask where you got the beacon position information from? Is there a public resource for this? It would come in useful for something I am working on.

This is big. I much prefer playing games via Steam. Download speeds are one of the main reason. There's no way ED can offer 10mb/s downloads. It used to take forever to patch before Steam.

Mi-8s navigating next time then :)

Sorry about that Charly. I plan on organizing some more missions once I'm back from the U.S. I'm also doing a bit of research on doppler navigation and radio usage so the Mi-8 pilots can navigate without assistance from the Ka-50. I made a slight error with the mission and we could see our position on the F10 map last time, but we only really used that to check everyone was together. Some peope weren't able to talk on TS much, but that was ok. Ended up a lot of fun. Oh - and everyone should join the Steam Mi-8 group - if you use Steam - http://steamcommunity.com/groups/DCSMi-8

Thanks all for joining! Was great fun! Thanks especially to Mad for navigating for us all. The flight lasted longer than expected, but I think everyone had a great time. The lost troops successfully made it back to home base.

Test server is up if you wanna check your connection. - Keyword "Slazia".. TS3 server is up - but im inactive for another 30 mins or so while I finish up the mission.

Thanks Mad. I'll update that for you in a moment. - Updated above. Slots: Reserved Mi-8 slots: Wolle Rodd Cibit Charly_Owl Wolf5 Zulumike Slazia Reserved Ka-50 slots: MadCat Guest Slots 3x Mi-8 2x U1-H1

Mission: Slazia's Night Flight Time: Sat 7th 14:00 UTC We've got to go and collect some new recruits who have gotten themselves lost. They managed to find a town and have radiod us with their location. The flight plan is below: Waypoint 0 Name/Task: Home Base Location: Sukhumi-Babushara LAT: 42°52'07''N LONG: 41°07'07''E Arrival: 20:30:00 Departure: 20:45:00 \\\\\ Waypoint 0 (Guest) Name/Task: Home Base (Guest) Location: Gudauta LAT: 43°6'43''N LONG: 40°34'6''E Arrival: 20:30:00 Departure: 20:45:00 \\\\\ Waypoint 1 Name/Task: Refuel / Regroup Location: FARP Skala & Otkrytka (124.5 / 127.5 AM) LAT: 43°23'47''N LONG: 41°59'12''E Arrival: 21:15:00 Departure: 21:30:00 Waypoint 2 Name/Task: Pickup infantry lost on exercise Location: Town of Tyrnyauz LAT: 43°23'22''N LONG: 42°54'59''E Arrival: 22:00:00 Departure: 21:10:00 Waypoint 3 Name/Task: (DP) Land and drop off troops Location: Nalchik (Airbase) LAT: 43°30'50''N LONG: 43°38'11''E Arrival: 22:35:00 Departure: N/A The approx mission time is 2h05m. But that includes around 25 minutes of waiting time. We can cut this down. People may want to leave at some of the wp landings. That is cool. Teamspeak 3: Up now if you need to test. I might need to close it down at some point, but will be up before event starts again. 114.158.92.125 Everyone MUST join. Even if you are not speaking, you need to be able to listen to others. DCS Version - Latest. No beta update.

Ok, I've put all your times into a spreadsheet to make everything easy to manage. It looks like we'll be flying at 14:00 UTC. I'll try to get the server up before then so everyone can get in, check everything is working etc. I'll post full mission details ASAP. But for now, 14:00 UTC. - TODAY :) Possible members: Slazia Zulumike Wolf5 Madcat (time?) Unfortunately it is out of Jorgwell's requested time zones. Sorry Jorg.