Konchog

Yeah - I’m hoping for a complex logic component so that I can tidy away the ten+ rules I have on some minidrones! They get so clunky. It’s weird writing with these assertions - a bit like some cross between prolog and scratch 🙂

This is super useful for the ancient artefact missions! Thanks!

So when the resource is buried under a load of terrain, how does your magic engine get it? Or do you just spam terrain eaters, which is what I currently do?

Yay! I see container!! Fantastic, Micha! It would be super-cool to add "Nearest Resource" to the VTOL / Directional Sensor also...

There is one bug with tags - the tag editor allows one to delete characters from the right using backspace, but then adding a character wipes any remaining text. for instance if you have the tag “fire gun on right”, and a was any to change it to “fire gun on left”, you always have to rewrite the entire text. Which is annoying...

Enemies is great. But being able to add waypoints, dummy resources, cans, terrain, etc. for testing autonomous drones would shave minutes of having to go on planet to run a test. For instance, doing 'collect ancient artefact' - I had to go through lighting all the beacons before I could begin to work on the artefact gathering itself - I got there, but it took 4 minutes of beacons for each test run... The most recent version is far better, but pick up and drop off and explore quests are hard to model!

So this caused a series of 20 second+ temporary hangs after having picked up the MO on Jashevosa. The hangs seem to persist outside of the mission. Mac OS Catalina, Nimbatus v0.9.6 Floater.drn 8c5bb056-9f52-4241-8468-4a3de7f4b429.nimbSave

What if it doesn't crash, but hangs?

omg.

Hi! Yes - it does - but I'm not sure how to pick the artefact up yet. (I'm playing autonomous) - it gets the correct MO each time (including the artefact), but I've not yet worked out how to pick up / recover the artefact yet. Designing a 'lamp lighter' autonomous drone was quite a challenge.

Having the ability to contain a set of logic gates / sensors / etc within a subsystem component would keep space way down, and possibly allow for private/internal key triggers, with public key inputs / outputs also, possibly via logic splitter / connectors Bearing in mind that the internal components would need less shielding, one could also drop the internal mass value too? With some simple registers, serial memory, and the equivalent of a PC, SP and ALU one would have a basic CPU. Because: Building RAM out of NAND gates loses it's cool after a while!

A docking component would be awesome. It would need to be available as a sensed object (and whether or not it is currently docked). For instance, It would really help for resource mining, especially if we also could manage resource/power/fuel transfer.. That way, the drone core can sit above the container, and then mining subs can go do the mining, and dock to the core, which would then drop resource into the container.

Yeah, I got there! The position tracker is sweet - but the camera tracker fails with factory-produced drones - unless there's a tab-or-something to switch between cameras on the same key?

SO neither the VTOL nor the balance sensor can be used to find resources... Ow! It makes the programmer/autonomous campaign mode nearly impossible, especially as getting back to the TOP of the container is really hard. (Basically, one has to ensure one first gets to a high altitude away from the container, and THEN keep that attitude until one is above the container.) Basically, I cannot quite see how to build an autonomous mining drone.

The indestructible funny eye-based statue seems to be the target of all of my sensors? I was missing something - It needs to be lit! Still not sure I know how to gather the final artefact..

With unconnected objects (especially factory-produced mini-drones) it would be good to be able to use the same key set for each group, without having to re-assign keys to all the components. Currently the drives work fine - they are isolated - but the prox. sensor, and distance sensor trigger keys that effect every drone across the planet. Is that by design? I get that there's a problem also with the camera sensor - maybe it would be a good idea to use the tab key to switch between cameras on the same key? Loving the game....

with large drones, especially in autonomy mode, not seeing key assignments really sucks. It means I have to start drawing them out on pieces of paper?!

When using full autonomy, especially for eg snake eggs, using a set of autonomous sub drones to actually do the mission works very well. However, the player cannot see what they are actually doing - because there's no zoom / pan of the planet. I get the camera sensor helps a bit - but then, especially when using the factory, it is hard to switch between each camera sensor instance.

Yeah - but only cursor rotation - which sort of sucks for full autonomy. I want to use full autonomy. The main problem I now have is not being able to zoom out so much from the core - especially when my sub-clones are doing all the work!

I've been working on the campaign mode - and using a drone cluster works quite well - but avoiding the container at the beginning is a royal pain. Each of the offspring has it's own offset timer, which works really well. (This was before I learned about the factory!)

Yeah - ok, I didn't think to connect the motorised hinge to a balance sensor - but it works well.. One has to adjust the response speeds very carefully for optimal effect, but it certainly does the trick. A real shame that the VTOL won't rotate things attached to it though...

@corona_wind, that would be good to see. I'm also looking for a good way to aim beam weapons at enemies. Currently I'm using a rotating arm which locks onto an enemy once the enemy crosses the distance sensor - but that's all I could do so far.

This forum doesn't work on Safari! One cannot create new content - the title / body fields just won't focus. --- well, it seems to work now!!

Currently some sensors cannot sense things other sensors can. Eg - the container is not a valid sense target for distance/proximity sensors. Maybe that's some upgrade thing - but it is counter-intuitive that I have to find different sensors to target the container. Maybe separate out the 'sense discriminator' from the sensor type, and upgrade the number of discriminators a sensor can hold at any given time? Eg - start off with 3 sockets - or even 1? Then any sensor / object-directed thing can be used for any set of discriminators?