Search results

Yes, but the core-game XMLs are still in the old format, and I wanted to wait to see a real implementation. Then I will also adjust this.

THX. I will implement it soon.

Do you have grafana experience? I'm struggling since a while to read out a value from a grafana dashboard (I don't have direct access to the underlying sensor).

And it is a bit more standardized. By using https://github.com/MarcusZuber/KittenRemoteControl/blob/master/openapi.yaml many tools can more or less automatically build you a client.

I wanted to be able to send more complex data in a bit more structured way. Like the dictionary for the different thrusters that should fire or a full maneuver node. With the bare socket both ends would need special parameters for each command and especially would need to know how much data to...

Migration to REST is done.

I'm currently migrating from the socket connection to a REST api. If you build something on top, it is worth waiting a few days.

I just submitted it in the blender addon repository. After it is reviewed it can be installed directly in the blender addon-window.

I removed the sub-parts for thrusters and engines.

Can you give this here a new try? Now you select only a folder in the export. If I didn't screw it the structure should be as you proposed.

Should the Material ID of the subpart be the PBR Material ID from the top? (same for mesh file id) Should I make one subpart for each mesh in the scene? Should I try to also export the mesh and material at the same time? (How do you export it right now?)

Here the first "hardware": https://discord.com/channels/1439383096813158702/1440090260431175700/1441742298688786565 I used the "shell_command" integration of homeassistant in the background calling: shell_command: enable_engine: echo "SET /control/engineOn 1" | nc MY_IPADDRESS 8080...

Were the thrusters pointing in the right directions? If you could attach me a tiny example (blender + expected XML) for the subparts etc. I can implement this as well.

Here https://forums.ahwoo.com/threads/blender-exporter.494/ I posted an initial implementation to handle engines and thruster in blender. If I get feedback from the part creaters, I will improve it.

Hi, I'm working on a blender plugin that creates the required XML files for parts. You can add thrusters and engines and specify the required parameters in the Parameter editor. Under Export you then find KSA xml which creates an xml file. The source code you can find here...

I'm currently trying to create a custom empty for thrusters and engines that directly have the relevant properties for ksa. I will share it when I got a working prototype. It will be basically the same but hopefully a bit more elegant.

I found the XMLs defining the rockets with the subparts and engine/thuster settings. How would this be nice to be implemented in blender from a "user" point of view? All the parts have many properties like specific impulse, on which input they are bound etc. My initial idea would be to add...

How are the config files formated? Could someone post one here?

Did anybody try to run it directly under mono? It would be cool, but I doubt that all libraries are not platform dependent.

Each rocket has a defined minimum throttle value (5% for the stock ones). I think they added this for realism, since you also can not run a rocket engine with to low thrust.