If you're stuck waiting on the AID function, try to use my AID script. If you have all the tiff and xml files in the same folder (with the corresponding names), it will auto-generate AID files for all images.
How about finishing the stock aircraft (fully simulated systems, fully simulated cockpit) first before starting new ones.
I'll take a look on the github and pull the latest version.
3D Studio is unavailable for most of the community. Wouldn't it be possible to have a standalone model importer accepting open-format industry standard file types (object+animation) and not just application-specific exporters?
I hate pointing fingers on Blender, but for someone new to AC3D (and has any Blender background) there's no reason to pick it at 150 USD.
Thank you! Way to go!
yes there is. We have highlighting for EditPad Pro, I made one for Notepad++ (expanded from the old Aerofly RC 5 toolset).
If I remember I can upload the notepad++ highlighting this evening. Its not really dynamic in Notepad++, so I need to keep it up to date manually.
But it highlights the code nicely and highlights key words and all known parameters.
Superb, thank you!
Btw, is there a syntax highlight setup existing for aerofly text formats for any text editors? It can help to unveil typos and banal syntax errors.
For e.g. notepad++ or sublime it would be nice.
So basically control surfaces are simulated as if the aircraft was a huge RC model with model servos moving the surfaces?
... So just increasing the flap angle already can affect things like: when I switch from one aircraft to the next, how much flap will the next aircraft have at initialization.
About this initialization. Is one better off re-starting AFS2 if switching aircraft-to prevent this issue (for now)?
The perfect is the enemy of the good.
I did not mention perfect, but complete. I'm an engineer so from my point of view, complete = feature complete with no deal-breakers.
I'll let perfect to scientists.
My wish list is simple: Just the aircraft where the designers have the most fun to do it. So it will be finished and deployed with love and enthusiasm. Nothing worse than doing stuff you don`t like to do.
Th devil lies in the details. Here, it's the 80-20 rule. Most tasks can be done to 80% completion at 20% of the time frame, while the rest 20% of progress is being done at the remaining 80%. There is no such favorite task that won't turn into a chore when it's no longer seeing high amounts of progress in a short time.
Unfortunately, it's that upper 20% of completion that gives something the preception of complete, that makes the difference.
The is no way around the grinding. It will always be more attractive to start something new and bring it up to 80% rather than finishing anything just to be 100%.
Most of us been there, done that. It's the question if we have the guts to face it.
I can't wait the A320 to be finished.
Yes, but not the source code, just the editor
I do plan on finishing the tmedit tool though, its quite far in progress but some of the broken features need to be repaired yet.
I see. Sorry for the confusion, for me github is not necessarily code (e.g. opencv libs prebuilt for mingw is on a github repo).
I've interpreted your post about that tool not yet ready for public as something to be published at some point, possibly in the sdk. Then I'll just keep entertaining myself with my pet project.
I've been also doing this in my spare time, like the other tool-related things. I have around 2 hours in the game,
I did not say it would be a text editor.
My plan was/is the following:
* C++ with wxwidgets, wxshapeframework made with code::blocks -> cross-platform, project template working
* GUI with visual block editor (+text editor view), editable templates
* Basic checks (unresolved references, broken signal flow, no inputs etc.)
* long-term goal: 3D model viewer/marker, question is how to get full ac3d support.
If you guys have what we could use (no support, use at own risk etc.), why not put on github?
Ok so there is a TMD tool underway. If it comes in a foreseeable future, I'll just hit the brakes with my TMD editor efforts...
If you don't hear from me again, I probably got banned, and if that's what this comes down to, then so be it. I have the utmost respect for the IPACS team, but their policy on forum moderation and total non-reply to my request about tagging mod-edited posts and then locking the thread has left a really rotten taste in my mouth.
I wouldn't assume they ban you for any such reasons. There is a forum member I won't name whose spam posts are regularly deleted but other relevant posts are kept and not banned.
You got it exactly. And that's for the raw photos you grab from the net.
In case you have to match the colors with an existing neighbouring DLC (e.g. Switzerland DLC or Orbx LOWI in this case), then you don't have those sources
Let this be our next problem after we solved what we can on our plate, ok?
I assume one can first do a test run with just one tile to import, which will go fast and the difference becomes apparent. Then we can have a manual adjustment option that can be applied to all tiles or e.g. color correction values for the N/S/E/W side of the bounding box can be given and applying them as a linear interpolation so the imported tiles would blend between their bounding sides or edges gradually so the new tiles will 'blend' the color diff between the sorrounding tile sets. Thoughts?
If you wanted to research what Ortho4XP grabs for elevation (if you speak Python) and document it, maybe write some test code that would all help.
Code for OrthoXP is here (well, a fork) https://github.com/voyageur/Ortho4XP
When AeroScenery is out in a week or so, there will be some documentation work to do also.
Sure, I'll hop on the Ortho4XP topic and I can also help in the documentation.