Don't you mean byte instead of bit, and Mb instead of MB? One byte is 8 bits on modern computers...
And I doubt a single screenshot can be 133 MB even if it's a .bmp. Is that a whole folder of screenshots or is your screen resolution over 10 000 x 10 000?
Is "to >=" supposed to be "=>" an arrow? Or do you mean that 133 MB is larger or equal to 10 MB?

It can be useful to be able to separate out and err though. And I can't copy from the terminal window, search through big output or even go back to the beginning if there's a lot of output. Would be nice if stdout and stderr could be used as an option.

Also, how do I choose what text editor is opened with the "Edit" button? I'm prefer to use Sublime Text...

Bug: print and error don't write to stdout.txt and stderr.txt anymore!

Bug: Using this code
state <- 0
function log(str) {
    Display(str,1000,2,0)
    print(GetGameTime() + " " + str + "\n")
    error(GetGameTime() + " " + str + "\n")
}
function Voxel_Step() {
    if(state == 0) {
        state = 1
        log(GetInfo(1) + "  " + GetInfo(2) + "  " + GetInfo(3))
        PlayerMove(0.0, 30.0, 0.0)
        log(GetInfo(1) + "  " + GetInfo(2) + "  " + GetInfo(3))
    }
}I get thrown up to Z = 5000 instead of 30. Or is PlayerMove supposed to use voxel distances? It takes floats (and does not accept ints) and there is only one PlayerMove function that can move the player...

When I try to pick up items that are too hard for my tool the sound and the "too hard" message are delayed sometimes. If I just click and wait it can take several seconds. If I double click or spam the sound from the first sound is played when I click the second time.
And one time when I tried to do it and held down the mouse button I grabbed the current item in my inventory in the sidebar and could move the items around. This was not in the inventory screen. Really weird...

I want FOV options. I normally only play 3D first person games if I can play with a vertical FOV angle of at least 130. This game isn't very action oriented and I spend most of my time in my text editor writing code, but I think it's time we got a setting for this in the game now.

If you make a slider then please show the numbers also so that I know what setting I choose.

Awesome! Though the assembly voxel doesn't have a recipe! http://blackvoxel.com/view.php?node=1584

That is qonvenient :>

_{...though you linked it in my bug report thread several days ago q:}

Can you post :

• The content of the Settings_Hardware.dat file : it's in the Document/Blackvoxel folder. It's a text file.
• The content of the Log.txt file : it's in the same directory you have the Blackvoxel executable. Also a text file.
• What's the brand and type of the Graphic Circuit used in the computer (AMD, nVidia or Intel ?). What's it's type (Radeon xxxx or Geforce xxxx)
• What is your screen setup ? How many screen ?
• You say you use "GUI scalling", can you tell me in which part of your driver do you set what setting to reproduce the problem.
• Why can't you use your laptop for other tasks when scalling is off ? Is this because of GPU usage at this resolution ? So you use lower resolution upscalled by GPU ?
  
• Your Windows version ?

Answers to your Questions in the same order.

Settings_Hardware.dat
Setting_Resolution_h      = 0
Setting_Resolution_v      = 0
Setting_FullScreen        = 1
Setting_ViewPort_Offset_x = 0
Setting_ViewPort_Offset_y = 0
Setting_ViewPort_Size_x   = 0
Setting_ViewPort_Size_y   = 0
Setting_Sound_Enabled     = 1
Setting_Sound_Volume      = 100.000000
Setting_Mouse_Factor      = 2.500000
Setting_Key_MoveForward   = 119
Setting_Key_MoveBackward  = 115
Setting_Key_MoveLeft      = 97
Setting_Key_MoveRight     = 100
Setting_Key_MoveUp        = 113
Setting_Key_MoveDown      = 122
Setting_Key_Jump          = 32
Setting_Key_Inventory     = 105
RenderingDistance_Horizontal = 8
RenderingDistance_Vertical = 3
Opt_SectCFactor = 1.000000
PixelAspectRatio= 1.000000

Log.txt
[1000.1]
[1000.2]
[1010.1]
[1010.3]
[1010.2]
[1020.1]
[1020.2]
[1030.1]
[1030.3] Info : SDL Infos [current_w:3200][current_h:1800][BitsPerPixel:32]
[1030.2]
[1040.1]
[1040.0]
[1050.1]
[1050.6]
[1050.2]
[1060.1]
[1060.2]
[1070.1]
[1070.2]
[1080.1]
[1080.2]
[1090.1]
[1090.2]
[1100.1]
[1100.2]
[1110.1]
[1110.2]
[1120.1]
[1120.3]
[1120.2]

Intel HD graphics 4400

1 display, 13" with 3200x1800 resolution

GUI scaling is a windows settings, reached from the display settings panel.
This:

Its kind of unusable because with a screen that small and with a resolution that high and no GUI scaling, everything becomes so small that I cant click it accuratly and text is so small that it is hard to read.

Windows 8.1