Show Posts

This section allows you to view all posts made by this member. Note that you can only see posts made in areas you currently have access to.


Messages - olive

Pages: 1 2 3 [4] 5 6 ... 10
46
General Discussion / Re: Newbie Guide?
« on: October 16, 2014, 08:55:19 pm »
Yep, Green Blackrocks can be found at 64 blocks bellow surface, the Blackrock orange layer at 128 and the BlueSky at 192.

You can dig a staircase for underground exploration and extraction.

Remember you need to build Constructor/destructor N°2 for digging through Blackrock Orange and N°3 to get through the Bluesky ones.

Don't forget to collect all metal ores and carbon in the way.

One of your first goal should be building the Extraction Robot XR-1 and an Atomic Compressor : Once these elements are made, mining will be fully automatic.

The Blackvoxel Team.

47
General Discussion / Re: SDL2 and how to close gui's?
« on: October 16, 2014, 08:53:47 pm »
Quote from: d3x0r on October 16, 2014, 03:56:09 am
My games aren't saving.
my last world2 I died, and saved hit escape and got out before being respawned.  Now I get console messags that say 'fatal fall...' something but don't die.   And when I move a couple steps and quit, it always starts where it was, including old worlds... hmm the binary download saves... wonder what I broke.

Hum, it could be related to development settings that may be enabled and could disable save.

Look at the ACompileSettings.h file for master switches. At line 76, change :

COMPILEOPTION_ALLOWSAVE 0

with :

COMPILEOPTION_ALLOWSAVE 1

Be sure to change this on line 76 only.

The Blackvoxel Team

48
General Discussion / Re: SDL2 and how to close gui's?
« on: October 16, 2014, 02:05:41 am »
Hi d3x0r and welcome,  :)

What you do seems very interesting.

We will look at the details in the next few day to respond to your questions.

Some informations we can give you quickly :

- The inventory "I" key is used to close all GUI dialog boxes. Can certainly be improved.

- All GUI elements : Windows, Gadgets, Buttons, etc are nested boxes of ZFrame type class or inheriting child classes. To create a button like a close button, a ZTileFrame should be a good choice. It must be added to the parent ZFrame for display and use.

- Buttons addition to GUI, GUI definitions and events are processed in the Window classes ZGameWindow_* classes. These classes are good exemples on how to make a dialog box in Blackvoxel.

Thanks for signaling some problems on sound server.

We'll try to give you more detailled informations in the next days. Some docs on Blackvoxel internals need to be written and we'll try to do that gradually with time.

Thanks for you interest in Blackvoxel,
The Blackvoxel Team

49
General Discussion / Re: OSX port
« on: October 15, 2014, 03:19:14 am »
Hi tintor,

Thanks  :)

We are planning to make an OSX version of Blackvoxel.

We think about launching an Indiegogo campaign to fund the purchase of a Mac and the development work.

The Blackvoxel Team

50
General Discussion / Re: Ubuntu 12.04 with vertical monitor setup
« on: October 15, 2014, 02:54:50 am »
Hi tintor and welcome,

Thanks a lot for your bug report, tintor.

We managed to reproduce the bug successfully, so it will be fixed in the next release.

In the meantime, you can use Blackvoxel in windowed mode with fixed resolution.

If you can't set the resolution in Blackvoxel, download the Settings_Hardware.dat file and put it in the Blackvoxel data directory which  is in your home. This is a text file and you can adjust the resolution as you wish.

Thanks again,
The Blackvoxel Team

51
Troubleshooting & Bug Reports / Re: The v1.34 bug report thread!
« on: October 11, 2014, 02:21:54 am »
Quote from: Chirno on October 10, 2014, 01:38:34 am
When moving in water it seems that I am slowed in one cardinal direction but not the other.
Reproduction: Go in water, look somewhere between N/NE/E/SE/SW/W/NW and pay attention to your movement. Kinda annoying.

Hi Chirno,

Thanks a lot for your report.

We've made a quick try on our development machines but it doesn't show up on these. That's not surprising : we already fixed some issues that show up only on some situations/environments/hardware. So we'll need to make investigation and test on other hardware/environnments for catching this bug.

As some areas with a lot of moving water require a lot of processing power on CPU and a lot of refresh on GPU, so it may be related to this. You can try lowering viewing distance in Settings_Hardware.dat and see if you have improvements.

Can you give us some informations on the machine used to run Blackvoxel : Operating System, processor type, number of cores and GPU used. Also, the number of FPS you get (use F12 key to show FPS) when you are in the water area and experiencing the issue.

Thanks again...
The Blackvoxel Team

52
Announcements / Re: Blackvoxel is now on GitHub !
« on: June 19, 2014, 03:52:35 am »
Hi Qon,

Yes :)

...but it's the official announcement !  8)

The Blackvoxel Team

53
Announcements / Blackvoxel is now on GitHub !
« on: June 19, 2014, 02:50:10 am »
We are happy to announce the release of Blackvoxel source code on GitHub.

You can find it here: https://github.com/Blackvoxel/Blackvoxel

All contributors are welcome !

The Blackvoxel Team

Source http://www.blackvoxel.com/view.php?node=1550

54
Troubleshooting & Bug Reports / Re: The v1.34 bug report thread!
« on: June 19, 2014, 02:13:34 am »
Hi Genius,

Thanks for all the details you provided. It helped us to reproduce all these problems successfully.

We added these on the Todo list for bug fix and improvement. So, it should be fixed in the next version.

In the meantime, here are some workarounds :

Make one blank voxel between Materializer and Dematerializer, so it will work in "non coupled" mode which is not affected by the bug.

For using Voxel Materializer with liquids, make some room under the materialization area : the liquid must flow down, so it won't be replaced with other appearing liquid voxels.

Have fun!

The Blackvoxel Team

55
Troubleshooting & Bug Reports / Re: The v1.34 bug report thread!
« on: June 17, 2014, 11:44:00 pm »
Hi Genius,

Welcome to the forum :)

Thanks for reporting your problem.

No, the optical fiber isn't supposed to lose resources. If it does so, it's a bug that we'll have to fix.

Can you say more about which elements are combined for reproducing the bug ? And which elements are you transmitting ?

We tried with a simple chain :

Voxel-Dematerializer,
Optical-Voxel-Transmitter,
Optical Fiber x5,
Optical Voxel Receiver,
Atomic Compressor

But it didn't seem to lose resources (at last with very simple try).

So, it would be useful to know which elements are used in your setup : the faulty element have a big chance to be one of these.

The Blackvoxel Team

56
Troubleshooting & Bug Reports / Re: The v1.34 bug report thread!
« on: June 12, 2014, 01:45:46 am »
Quote from: Qon on June 11, 2014, 11:15:14 am
1600x820 in windowed mode seems to work quite well :>

Ok, good news :)

57
Troubleshooting & Bug Reports / Re: The v1.34 bug report thread!
« on: June 11, 2014, 09:19:22 am »
Hi Qon,

Thanks for these precise informations. This has allowed us to reproduce the problem successfully.

Unfortunately, it's a total mess in Windows 8 with this option enabled. With 7, it works successfully, only upscaling GUI, not the OpenGL Games.

The configuration file tell us you are in "automatic" mode. The log has shown that Blackvoxel successfully detected the resolution of your screen and tried to set it. All should have worked ok and the system should have set the asked resolution. That's what the system seems to do as the response was "ok"... but our test shown that the display is zoomed by the factor of the "GUI scaling factor". It does that even if Blackvoxel asked the native resolution of the screen. That's even worse: it does that whatever resolution we set. And whatever resolution we choose, it display it fullscreen... then upscale over the screen limits :o So it simply doesn't work in fullscreen.

At this time, we don't know exactly from where come the problem. So, for the time we'll try to figure out how to fix it, we found a workaround : use windowed mode with a specially computed resolution.

You can modify directly Settings_Hardware.dat and set in it whatever resolution you want.

As Windows 8 is also scaling in windowed mode(but not making it fullscreen before upscaling), you'll have to compute according to the ratio set in the "scaling GUI interface". For 200%, you'll have to divide resolution by 2 and substract some pixels for GUI toolbars and windows borders.

So, this is what you could modify in your Setting_hardware.dat for 200% scaling:

Setting_FullScreen       = 0
Setting_Resolution_h   = 1500
Setting_Resolution_v   = 800

So, Windows 8 will upscale it on 3000x1600.

Tell us if this works...

The Blackvoxel Team

58
Troubleshooting & Bug Reports / Re: The v1.34 bug report thread!
« on: June 11, 2014, 12:42:18 am »
Quote from: Qon on June 10, 2014, 04:01:03 pm
I'll start with:
The game does not work correctly with GUI scaling in windows. I can only see 1/4 of the screen, the center piece. Everything else is cut off, which means that the settings menu is unusable in some cases and so on...
When I alt-tabbed out and back in again I could only see the top left qorner instead. If I try to change GUI scaling while the game is running the graphics driver crashes and restarts and the game stops working and has to be restarted too.
I need GUI scaling on my laptop to be able to use it since my resolution is 3200x1800, having scaling turned off while BV is running means I will not be able to use it for other things at the same time. And BV is a game that you often minimize while waiting for mining robots or computers to complete their work.

Hi Qon,

We have tried to reproduce the issue, but unfortunately, it didn't show on our hardware (nVidia). Maybe we didn't put the correct settings, maybe it's related to some manufacturer hardware. So we need to investigate deeper to reproduce it and understand why it's working bad.

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 ?

Actually, Blackvoxel display resolution (and parameters for scaling) are set only once: at program start. That's here : https://github.com/Blackvoxel/Blackvoxel/blob/master/src/ZGame.cpp in ZGame::Init_GraphicMode(). The resolution or scaling is never changed during program execution.

There is two way Blackvoxel can use to set the resolution and ratio. The first way is the "automatic" setting : in this case Blackvoxel use the resolution of your desktop. The second way is the "Manual" mode, if you set a particular resolution in the Blackvoxel's GUI or in the Settings_Hardware.dat file. In this mode, Blackvoxel will use only the parameters you set.

The Blackvoxel Team

59
Announcements / Re: Blackvoxel is now a free software !
« on: June 10, 2014, 07:34:18 pm »
Hi Qon,

Good news and good job :)

60
Troubleshooting & Bug Reports / Re: The Manual Error Thread
« on: June 10, 2014, 07:39:19 am »
Thanks a lot, Qon.

That's fixed in the manual, now :)

Pages: 1 2 3 [4] 5 6 ... 10