Mission Flight Plan & Google Earth Path - ED Forums
 


Notices

Reply
 
Thread Tools Display Modes
Old 08-14-2011, 07:22 PM   #1
ivanwfr
Member
 
Join Date: Apr 2011
Location: France - Limours
Posts: 310
Default Mission Flight Plan & Google Earth Path

Preparing Poschi's operation pk v1.miz mission with Google Earth for an Aerial Photography Reconnaissance.

  • The attached file must be renamed with .kml extension before opening it with Google Earth.
  • And, as this is an xml file, no virus can hide in there!


[updated=110816]: Synced with Smoke_Path.miz bellow
Attached Thumbnails
Click image for larger version

Name:	Smoky_Path.jpg
Views:	519
Size:	499.2 KB
ID:	55307  
Attached Files
File Type: txt GoogleEarth_DCS_A-10C_Mission_Path.txt (24.7 KB, 576 views)

Last edited by ivanwfr; 08-17-2011 at 12:17 AM. Reason: Added Snapshot
ivanwfr is offline   Reply With Quote
Old 08-14-2011, 10:53 PM   #2
ivanwfr
Member
 
Join Date: Apr 2011
Location: France - Limours
Posts: 310
Default

Still looking for a convenient way to inject this flight plan as mission Way points...

Good news:
  • These coordinates are easily accessed from kml Placemark-LineString-coordinates element.
  • With AutoHotkey, I could build a converter for GE's decimal LON, LAT, ALT sequence to deg,min,sec:
Spoiler:

1: 42° 51' 56" N 41° 7' 5" E
2: 42° 51' 55" N 41° 7' 16" E
3: 42° 51' 55" N 41° 7' 25" E
4: 42° 51' 21" N 41° 8' 14" E
5: 42° 51' 16" N 41° 8' 9" E
6: 42° 51' 50" N 41° 6' 55" E
7: 42° 53' 8" N 41° 5' 35" E
8: 43° 2' 3" N 41° 2' 11" E
9: 43° 3' 8" N 41° 2' 26" E
10: 43° 5' 4" N 41° 1' 54" E
11: 43° 5' 59" N 41° 1' 59" E
12: 43° 6' 57" N 41° 2' 36" E
13: 43° 8' 20" N 41° 2' 49" E
14: 43° 9' 0" N 41° 3' 0" E
15: 43° 9' 57" N 41° 3' 6" E
16: 43° 10' 47" N 41° 2' 34" E
17: 43° 11' 36" N 41° 1' 59" E
18: 43° 11' 56" N 41° 1' 51" E
19: 43° 13' 40" N 41° 2' 51" E
20: 43° 13' 44" N 41° 3' 53" E
21: 43° 14' 27" N 41° 4' 13" E
22: 43° 14' 58" N 41° 3' 46" E
23: 43° 16' 15" N 41° 3' 26" E
24: 43° 16' 51" N 41° 3' 45" E
25: 43° 17' 14" N 41° 4' 45" E
26: 43° 18' 2" N 41° 4' 55" E
27: 43° 18' 28" N 41° 5' 4" E
28: 43° 19' 19" N 41° 5' 27" E
29: 43° 20' 6" N 41° 5' 16" E
30: 43° 20' 25" N 41° 5' 56" E
31: 43° 20' 46" N 41° 6' 12" E
32: 43° 21' 8" N 41° 6' 8" E
33: 43° 21' 18" N 41° 5' 35" E
34: 43° 21' 18" N 41° 4' 56" E
35: 43° 20' 15" N 40° 59' 38" E
36: 43° 20' 19" N 40° 57' 3" E
37: 43° 19' 38" N 40° 55' 43" E
38: 43° 19' 37" N 40° 55' 38" E
39: 43° 19' 23" N 40° 53' 32" E
40: 43° 19' 22" N 40° 52' 11" E
41: 43° 19' 45" N 40° 51' 12" E
42: 43° 20' 37" N 40° 50' 26" E
43: 43° 21' 20" N 40° 49' 39" E
44: 43° 22' 25" N 40° 49' 0" E
45: 43° 24' 1" N 40° 48' 53" E
46: 43° 24' 57" N 40° 48' 57" E
47: 43° 26' 4" N 40° 48' 52" E
48: 43° 26' 54" N 40° 47' 48" E
49: 43° 28' 10" N 40° 45' 59" E
50: 43° 28' 49" N 40° 41' 50" E
51: 43° 30' 6" N 40° 39' 26" E
52: 43° 31' 43" N 40° 37' 55" E
53: 43° 32' 16" N 40° 36' 11" E
54: 43° 33' 17" N 40° 34' 59" E
55: 43° 34' 46" N 40° 33' 13" E
56: 43° 35' 15" N 40° 31' 30" E
57: 43° 35' 15" N 40° 31' 31" E
58: 43° 35' 15" N 40° 31' 31" E
59: 43° 35' 14" N 40° 31' 31" E
60: 43° 35' 14" N 40° 31' 32" E
61: 43° 35' 14" N 40° 31' 32" E
62: 43° 36' 11" N 40° 30' 1" E
63: 43° 36' 44" N 40° 28' 56" E
64: 43° 37' 3" N 40° 27' 22" E
65: 43° 36' 55" N 40° 23' 54" E
66: 43° 39' 5" N 40° 20' 24" E
67: 43° 40' 8" N 40° 19' 44" E
68: 43° 40' 23" N 40° 17' 19" E
69: 43° 41' 10" N 40° 14' 50" E
70: 43° 40' 44" N 40° 12' 43" E
71: 43° 38' 5" N 40° 6' 36" E
72: 43° 37' 41" N 40° 4' 42" E
73: 43° 36' 54" N 40° 3' 44" E
74: 43° 36' 34" N 40° 2' 49" E
75: 43° 36' 12" N 40° 2' 3" E
76: 43° 35' 19" N 40° 0' 37" E
77: 43° 31' 55" N 39° 59' 23" E
78: 43° 29' 40" N 39° 59' 33" E
79: 43° 28' 20" N 39° 58' 51" E
80: 43° 27' 2" N 39° 57' 30" E

Bad news:
  • - The mission editor has no input field for them.
  • - Mouse click on the map is the only way.
  • - Messing up in LUA mission file looks like a bad idea.
...other ideas ?

BTW... an unavoidable offset between GE and DCS coordinates (to be expected and the amount is really not an issue here)
Attached Thumbnails
Click image for larger version

Name:	GoogleEarth_Start_Point.jpg
Views:	312
Size:	204.7 KB
ID:	55230  

Last edited by ivanwfr; 08-14-2011 at 11:05 PM.
ivanwfr is offline   Reply With Quote
Old 08-16-2011, 03:00 AM   #3
ivanwfr
Member
 
Join Date: Apr 2011
Location: France - Limours
Posts: 310
Default A really messy miz

Have a look at as much smoking factories you can along the path.

Must fly over at 100 feet max above each of 60+ plants ... then try to land on the messy airbase

Yet to be checked for altitude and scoring. and to be updated soon as many details still need fixing.

Metric and Imperial units mess is a nightmare: meters, feet, m/s, knots, MSL AGL, deg, min, sec, decimal! Each of those have their way to turn simple math into chaos...

Some tips:
- Each waypoint name contains (or should contain) max MSL spotting altitude (some are wrong).
- Past 40th waypoint, Flight Plan won't chain remaining ones (max FP reached)... CDU must be set to allow manual Mission WP selection (DMS FWD/BKW).

Still, I could not find a way to reflect score events into debriefing window and mission results ;(
...looking for clues...
As I don' t want to flood the thread, I keep with updating my own messages, until someone says something...

At last, I could get to a reported score of 80, and could see that the A-10C is ready for Carrier landing... some TV Tower cable did a good job as you can see below with my very short landing that got me spinning for a while but hey, no damage!

I still missed some plants along the way but as the author, I had to check many times, and the more I do it, the better it gets. Kind of addictive with the intensive HUD attention for how the 2 or 3 next way-points are aligned in order to be prepared for a hard turn, a steep climb or a dive. Then, after some attempts, special attentions comes to the few tricky moves you can do only after having failed or died.

[updated=110816]
- Much better adjusted altitudes.
- Scoring up to 300 feet above plants (from 100) ... altitude numbers have still mysterious behavior...?
- Could get something to show up in debriefing window.
- More appropriate sounds.
- Scoring messages, 1-9, then every ten more.

...Score amount still unclear. (Result vs. Score How To?)

If someone has some clever or tricky suggestion, I'm ready to add some fun in there.

A good thing would be to put that Reco to good use in a Campaign ... But I still have everything to learn there.


[updated=110817]
- Simplified triggers logic and some Debriefing-Results better synched.

BTW, the attached miz will never get many hits as I keep updating it everyday... so when it says 0, maybe it's not because no one cares...

Attached Thumbnails
Click image for larger version

Name:	messy_airport2.jpg
Views:	335
Size:	203.0 KB
ID:	55285   Click image for larger version

Name:	Smoky_Path_Map.jpg
Views:	411
Size:	639.8 KB
ID:	55304   Click image for larger version

Name:	Smoky_Path_NoCarrier_VeryShortLanding.jpg
Views:	372
Size:	347.8 KB
ID:	55305  

Click image for larger version

Name:	Smoky_Path_Score80_1xRed_Tower_dead.jpg
Views:	402
Size:	289.4 KB
ID:	55306   Click image for larger version

Name:	Smoky_Path_Clean_Landing.jpg
Views:	324
Size:	276.4 KB
ID:	55351  
Attached Files
File Type: miz Smoky_Path.miz (1.11 MB, 123 views)

Last edited by ivanwfr; 08-18-2011 at 12:32 AM. Reason: Updated
ivanwfr is offline   Reply With Quote
Reply

Thread Tools
Display Modes

Posting Rules
You may not post new threads
You may not post replies
You may not post attachments
You may not edit your posts

BB code is On
Smilies are On
[IMG] code is On
HTML code is Off

Forum Jump

All times are GMT. The time now is 08:55 PM. vBulletin Skin by ForumMonkeys. Powered by vBulletin®.
Copyright ©2000 - 2019, Jelsoft Enterprises Ltd.