Reading Scenarios

[evaamo]

Hi Baloogan, hope you and your family had a Merry Christmas!

As a CMANO beta tester, I'm a fan of your videos since long ago. Although I haven't tried them yet, I've been reading about your Geospace and Joint Command utilities and you seem to have obtained some internal knowledge about the scenario & save files' structure that I find useful, as it could help me achieve some goals for a side project of my own for CMANO.

If it's ok with you (and if you are able to answer, of course), I would like to know:
1)are you reading the scenario file directly on disk or are you performing any hooks to the game engine/memory?
2) I've been reviewing the scenario file structure, and there's an XML tag "scenario_compressed". It looks like an encoded (Base64?) string which is later uncompressed and parsed by the game engine. Is there any technical documentation on this? are we walking in a gray line in terms of the EULA? (I know you are now part of the dev team tho').
3) are you able to read/pull info in real time of each and all of the items involved in the scenario (things like units and their magazines, sides, emcon, altitude/depth, heading/course, speed, waypoints, etc etc etc. Also things like the current weather conditions, trigger of predefined events and also of random events.) I understand some of these are " settable" via LUA scripts but not readable, much less in real time.

I have some others, but I don't want to overwhelm you with my first post here

Thanks a bunch for any pointer you are able to provide.
Cheers
-E

[bostonmyk]

What side project with CMANO?

MIke

[evaamo]

Hi Mike, it's a personal project...mostly an experiment really. i want to re-write a semi-autonomous Air Tasking Order generation tool that I designed a few years ago for a real world user and try to integrate it to CMANO. Can't comment much on a public forum tho', but if my experiment works I will release it as a free tool for the community.

cheers
-E

[ckfinite]

Best approach would be to write a Lua interop layer - generate Lua code in the Lua directory, then load it in from in-game. The savegames are more work than they're worth for your purposes, IMO.

[bostonmyk]

Sounds pretty cool evaamo however at this point we're not comfortable decrypting the scenarios. If you can see if you can catch us online and we probably figure out a work around.

Mike

[bostonmyk]

Hi Dimitris and I had a chat today about this. If you can provide us the details of the "inputs" and "outputs" that your ATO program utilizes, we could put the appriopriate hooks on our Lua API and have his prog call them.

Thanks!

Mike

[evaamo]

Hi Mike! thanks for your reply. I will be away for a week or two from the forums, but I will write a tech requirements draft and share it with you guys over the beta testers forum at matrix and see if we can work something out.

I have a question out of curiosity tho': the reason I posted here instead of the beta forum initially was because I had the idea the Baloogan was able to open the scenario files and read them directly for his own apps. Isn't that the way he is able to interact with CMANO? I respect your concerns and decision of not wanting to open the scenario files for third parties, just want to understand if Baloogan does indeed use this method or if there is any other way around it. Don't get me wrong, I love the idea of using whatever hooks you're able to provide instead, I'm just curious

Thanks again,
cheers
-E

[evaamo]

[ckfinite]

Should be possible reasonably soon, then (1.08, probably). The Lua hooks for all of that aren't exposed as of right now, but are planned to be soon.

[Baloogan]

[evaamo]

LOL... fair enough Baloogan... no soup for you!