Sharing Pre-flight Planning concept

[Panthir]

It works

 

Many Thanks

[Lt-Laverdure]

Hello, first thank you a lot for this tool, it is going to come very handy in MP !

I've tried it but im getting the known bug of "Import failed". I try to solve it as described but it isnt working, could somebody post a screenshot of the action to be taken?

 

 

EDIT : Made it work !

Edited November 18, 2017 by Lt-Laverdure

[Sgt_Cyanide]

Need a little help right now. Can someone help me out on how the waypoint time is calculated on the DCS mission editor?

 

Is the time calculated between the previous waypoint and the currently selected?

 

TOT is almost finished but I'm confused right now! :helpsmilie:

 

Edit:

 

NVM, I figured it out myself!

Edited November 19, 2017 by Sgt_Cyanide

[Neon]

Amazing! You, sir, are my hero.

 

 

Sent from my iPhone using Tapatalk

[Panthir]

Need a little help right now. Can someone help me out on how the waypoint time is calculated on the DCS mission editor?

 

Is the time calculated between the previous waypoint and the currently selected?

 

TOT is almost finished but I'm confused right now! :helpsmilie:

 

Edit:

 

NVM, I figured it out myself!

 

In my opinion, due to the fact that our subject is route planning and not execution you will have to simply add a speed option for each route's leg. In my opinion mach number should be ok as long as it re presents nautical miles per minute (0.8 mach = 8 miles per minute). Set by default a .550 mach number. In this context when you prepare a route by setting the desired leg speeds you will have the calculated time to target and consequently the time between to waypoints. Then if you wish you can add an option for Estimated Time of Take Off calculation by adding a Desired Time to Target price.

 

Cheers

Edited November 19, 2017 by Panthir

[Panthir]

Mach number is easier to be kept by the players during flying (any altitude) otherwise if you set ground speed in knots or miles it should be difficult cause they will have to calculate.

[Holton181]

Mach nummer are a fraction of the speed of sound, dependent on air temperature, and not NM/minute. Mach 1 represents different speeds (distance per unit time) in different temperatures. So it also necessitates calculations, less intuitive ones too.

[Sgt_Cyanide]

Thanks for you help. Currently I have only implemented ground speed, like in the mission editor. My calculated time on target is accurat as in the mission editor. But when I load it into the viggen, my time is offset for 200 seconds or so. Maybe I don't understand their logic behind the init.lua right now... Wish RagnarDa would explain their init.lua a bit more.

 

Later I'll have a look into mach numbers.

 

I do a lot of testing right now and it's frustrating :).

 

From the point of view of a programmer, how should mission time from spawn of the plane work in multiplayer? Am I missing something?

 

Line in init.lua:

"missiontime = 0, -- Optional. ETA in seconds from the start of the mission or when the aircraft is spawned."

Edited November 20, 2017 by Sgt_Cyanide

[Ice_Cougar]

I fixed the issue on Friday. Works great.

Thanks again for making this :)

 

 

Sent from my iPhone using Tapatalk

[Panthir]

Mach nummer are a fraction of the speed of sound, dependent on air temperature, and not NM/minute. Mach 1 represents different speeds (distance per unit time) in different temperatures. So it also necessitates calculations, less intuitive ones too.

 

When you fly, any altitude, wind free (zero wind) then the mach number you keep, multiplied by ten gives you the ground speed expressed in NM per Min. That's it so simple.

Let's say you fly 0.75M 35.000' (zero wind) you will cover 450nm per hour. In case of opposite wind eg 40knots after one hour you will have covered 410nm.

Edited November 20, 2017 by Panthir

[renhanxue]

When you fly, any altitude, wind free (zero wind) then the mach number you keep, multiplied by ten gives you the ground speed expressed in NM per Min. That's it so simple.

Let's say you fly 0.75M 35.000' (zero wind) you will cover 450nm per hour. In case of opposite wind eg 40knots after one hour you will have covered 410nm.

 

That’s a neat rule of thumb for ballpark estimates, but it’s off by more than 10% at sea level even at ISA.

[Panthir]

That’s a neat rule of thumb for ballpark estimates, but it’s off by more than 10% at sea level even at ISA.

 

That's right!

[Sgt_Cyanide]

The only thing stopping me to implement TOT is that I don't understand how the init.lua -> missiontime = X works, especially in a multiplayer session.

 

I would be really happy if someone can explain me how this works. :helpsmilie:

[Wizard1393]

Shoot RagnarDa a PM and see if he will enlighten you.

[Sgt_Cyanide]

Shoot RagnarDa a PM and see if he will enlighten you.

 

I've send him a PM three weeks ago, but I'll try it again. Maybe he had a lot of work to do.

 

Edit:

Can't send him a PM. "RagnarDa has exceeded their stored private messages quota and cannot accept further messages until they clear some space."

Edited November 22, 2017 by Sgt_Cyanide

[Vatikus]

I believe that there is a bug with TOT...

[Panthir]

I've send him a PM three weeks ago, but I'll try it again. Maybe he had a lot of work to do.

 

Edit:

Can't send him a PM. "RagnarDa has exceeded their stored private messages quota and cannot accept further messages until they clear some space."

 

The same happened to me a couple of weeks ago. Try again and he will reply. I am sure.

[Holton181]

I don't remember if it have been reported before, but I get the "Import failed..." error whenever I have a DMP planed route in my init.lua. Haven't tested with a ME route yet.

Makes it impossible to edit a route already exported, always necessitates removing everything in 'Data_cartridges'.

[Sgt_Cyanide]

Here is a small update on my im- exporter. Now there should be less errors on import or export.

 

You can see a preview on how TOT works on the waypoints, but it's not enabled yet!

The link is on my first post on this thread.

 

Changelog

 

Version 0.0.2:

- Improvements on the Im- Exporter.

- New application icon.

- Unfinished implementation of TOT.

[Holton181]

Nope, no success for me, same issue :(

 

As a side note, was there a default flight-plan in the init.lua before today's DCS update with entries like this?

{

cartridgenr = 1, -- Can be 1 to 5

waypointnr = 0, -- From 0 to 10 where 0 i starting base LS and 10 is L1. Nearest pre-programmed airbase will be used.

latitude = 41.60917, -- Degrees

latitudeminutes = 0, -- Optional

latitudeseconds = 0, -- Optional

longitude = 41.60028, -- Degrees

longitudeminutes = 0, -- Optional

longitudeseconds = 0, -- Optional

missiontime = 0, -- Optional. ETA in seconds from the start of the mission or when the aircraft is spawned.

velocity = 0, -- Optional. Sets a forced speed in m/s.

etalocked = false, -- Set to true to make the waypoint use the missiontime. Waypoint will be converted to targetpoint (Målpunkt)

velocitylocked = false, -- Set to true to use the forced speed.

istargetpoint = false, -- Set to true to set the waypoint as a targetpoint.

},

[LuftStriegler]

You de man, bro, you de man! :thumbup:

[Sgt_Cyanide]

Nope, no success for me, same issue :(

 

As a side note, was there a default flight-plan in the init.lua before today's DCS update with entries like this?

{

cartridgenr = 1, -- Can be 1 to 5

waypointnr = 0, -- From 0 to 10 where 0 i starting base LS and 10 is L1. Nearest pre-programmed airbase will be used.

latitude = 41.60917, -- Degrees

latitudeminutes = 0, -- Optional

latitudeseconds = 0, -- Optional

longitude = 41.60028, -- Degrees

longitudeminutes = 0, -- Optional

longitudeseconds = 0, -- Optional

missiontime = 0, -- Optional. ETA in seconds from the start of the mission or when the aircraft is spawned.

velocity = 0, -- Optional. Sets a forced speed in m/s.

etalocked = false, -- Set to true to make the waypoint use the missiontime. Waypoint will be converted to targetpoint (Målpunkt)

velocitylocked = false, -- Set to true to use the forced speed.

istargetpoint = false, -- Set to true to set the waypoint as a targetpoint.

},

 

You need to remove the default entries. The default file will be recreated on every update...

 

The data cartridge section needs to look like this:

 

Data_cartridges = {

}

 

I've included a sample files in the documents folder.

[Holton181]

You need to remove the default entries. The default file will be recreated on every update...

 

The data cartridge section needs to look like this:

 

Data_cartridges = {

}

 

I've included a sample files in the documents folder.

 

Thanks, but I did that. When removing the flightplans I can import it (no real use), after creating a new one I can export it, but not import it again afterwards.

I'm not at my computer at the moment, but later today I can share my init.lua for you to look at if it would help.

[Sgt_Cyanide]

Attach your init file. Maybe I spot the error.

 

You can try to import the sample init in the documents folder, maybe this works.

[Holton181]

I have now tried to import the sample file but no luck.

Attached my own init.

init.lua