-
Please see the most recent updates in the "Where did the .com name go?" thread. Posts number 16 and 17.
-
IMPORTANT DOWNLOADING INFORMATION - ALL MEMBERS PLEASE READ
Please see this thread for updates. Update Thread
SOH ADMINISTRATION
Deep Inside a Gauge File
- Thread starter Ali Cat
- Start date
Ali Cat
Charter Member
Hey, Shessi and so good to speak with you again.
Yes, the output is the gauge names straight out of the A6M2 standard gauge file (a binary which hunt). I plan to push the code to read all gauge names in one's gauges directory. Its not much of a utility but I've noticed some have requested it. I also wanted something for my first c++ project.
A bit of an explanation on this one. I've long been intrigued on just how CFS2 talks to all those dll's. I've learned a lot and while there's still hope that this effort will lead to something useful, the news is not good. While some CFS2 dll's export functions that look like c++ (you can see the function names and passed argument types), most do not. All the dll's (that I've noticed) export two names: “ImportTable” and “Linkage”. The bad news is that these are not function names. They are data structures that can (and do in the case of gauges) also contain pointers to functions.
After this project I have a number ideas for the next one but, XML to CFS2 gauge – yikes – how juicy. I had not thought of that. A few ideas for what's next.
-Gauge maker: To do right this would be a biggy (not hard just a lot of coding). And with such a tool it would be easy to add an XML import.
-Read a BGL or better yet a MDL file to develop an exporter. (yes, I'm aware of ModelConverterX).
-Continue working on the dll exports.
Ideas welcome but no promises – I'm easily distracted Ya' know.
AC
Yes, the output is the gauge names straight out of the A6M2 standard gauge file (a binary which hunt). I plan to push the code to read all gauge names in one's gauges directory. Its not much of a utility but I've noticed some have requested it. I also wanted something for my first c++ project.
A bit of an explanation on this one. I've long been intrigued on just how CFS2 talks to all those dll's. I've learned a lot and while there's still hope that this effort will lead to something useful, the news is not good. While some CFS2 dll's export functions that look like c++ (you can see the function names and passed argument types), most do not. All the dll's (that I've noticed) export two names: “ImportTable” and “Linkage”. The bad news is that these are not function names. They are data structures that can (and do in the case of gauges) also contain pointers to functions.
After this project I have a number ideas for the next one but, XML to CFS2 gauge – yikes – how juicy. I had not thought of that. A few ideas for what's next.
-Gauge maker: To do right this would be a biggy (not hard just a lot of coding). And with such a tool it would be easy to add an XML import.
-Read a BGL or better yet a MDL file to develop an exporter. (yes, I'm aware of ModelConverterX).
-Continue working on the dll exports.
Ideas welcome but no promises – I'm easily distracted Ya' know.
AC
Never heard of a Bglmac.inc. A goggle of it shows some talk of a bglmac.inc for BGLC 8.0
https://www.avsim.com/forums/topic/77048-2-versions-of-bglc-80/
https://www.avsim.com/forums/topic/77048-2-versions-of-bglc-80/
Ali Cat
Charter Member
Thank you, Allen. I had Googled it a bit but had no luck. A few weeks ago I wrote code that read the header to a BGL file (easy). It's a tiny start to a possible project that I don't know would even be useful. The idea started with the thought of importing a model into a game engine -- Godot, for example has caught my eye. ModelConverterX may be all we need here I just haven't been down that road enough to know. Guessing it would be a crazy amout of work but I like very much the thought of all the incredible work done herein could possibly live on much longer.
AC
AC