Infinite death loop.

If you dig a deep hole at location x:0 z:0 you will end up in an infinite death loop if you die since you always respawn at x:0 y:0 z:0.

Either put a voxel below the player spawn point on respawn or scan for a safe place to respawn the player. (The later is probably prefered, or you could be stranded on a single voxel without anything in your inventory to build your way out.)

Thanks. We will fix that 

Tried:

Code: [Select]

// Pause dynamiq voxel reaqtion engine!
function log(str) {
    Display(str,1000,2,0)
    //print(GetGameTime() + " " + str + "\n") //print doesnt work properly, use error instead
    error(GetGameTime() + " " + str + "\n")
}
function Voxel_Load() {}
function Voxel_Step() {
    log( "Qomputer @ " + GetX() + "," + GetY() + "," + GetZ() + " Look(5) " + Look(5))
    for(local q=0; q<50000000; ++q);
}
function Voxel_Unload() {}Looks kinda qool when everything stops. It gives you time to fix stuff if some big chain reaction is almost going to kill you. with 50 Gcycles there's about a physics step/second. If I use more than that then the game qrashes when the qomputer is picked up or when you try to change the sqript it should exequte :/
Too bad beqause stopping time is a very qool ability. It works but it qrashes as soon as you restart the time and then it\s kinda pointless!

That's an interesting test.

The idea of stopping or slowing down the MVI engine is interesting, we could add a mechanism that could do it.

The Blackvoxel Team

96 XR1s (8x3). First large sqale testing of the sqript just begun!
I worked a little more on my auto faqtory and it's now good enough to make all the robots and qompressors, which is why I haven't been able to test until now and how I got that many without haxxing the save file
You definitely deserve a reward for this fabulous piece of qode! Only my faqtory is epiq enough as payment. It's not qomplete though and the parts that are in are somewhat buggy atm. I'll post a beta when it's doesn't qrash or destroy your stuff

Unlimited resources + automatiq faqtory that makes anything is a pretty good qombination

Is really awesome 

The Blackvoxel Team

I tried to make the script only do one operation for every Voxel_Step to make it as light weight CPU wise as possible. That was before I realized that Voxel_Step is only called 3.5 times a second for the programmable computer. I just assumed it was called once every frame.  I didn't yet know the limitation on how much you could do every step.

That piece of code is changed now.

But it still needs to keep track of how many robots is has in it's storage so it knows when the robots has finished dumping there storage into the compressor.

Yes, the robot work isn't synchronized with display frame rate. That's synchronized with the Voxel interaction system. The robots can run up to 5 cycles per second or slower depending on the global voxel interaction workload.

The consequence of the way the system works is that you can use a significant amount of cycle in your programs without harming or getting stuttering problems. Of course, you should avoid taking too much power or block it completely. But there is some room.

Where is the limit and how to know if you are ok ? Look at the voxel interaction speed : If you are taking too much power, the voxel interactions will slow down.

Gaaaahh!! Awesome overload! Yes please to everything you mentioned

 

Yes, melted alloys composition are mixing when in contact (the heat also spread into the "alloy bath"). So you must cool the melted voxel after mixing. 

The Blackvoxel Team

You can cool the molten alloys with water 

Use water generator or pump to get water!

Fortunately, with the new 3D placement functions we just added to the code, it will took much less time to make it. At the time, we have not limited these functions to one action per cycle, so it will be really faster. We might eventually add a limit in the future for that, but we'll keep a setting somewhere to override.

So, as the first problem might be resolved, let's look at the second one.

For the world render distance (and loading distance) problem there is some ways  :

(1) Render by parts. The advantage of this is that there will be virtually no limit.

(2) There is a way to change world loading limit and viewing distance. It can be changed in the configuration file (RenderingDistance_Horizontal & RenderingDistance_Vertical). One unit more will add 2x16 blocks(it's a radius) in horizontal and 2x64 blocks in vertical.

Unfortunately, you'll can't get really high in the Windows version as it will get out of memory and will crash. So it's not recommended to get higher than the standard settings(It may be nasty and appears to work... then crash after some time or when you move).  If you want to use higher settings now, the only safe way at this time is the the 64 bit Linux version.

The Blackvoxel Team