Fractal Space

Fractal Space

Not enough ratings
Pre-Alpha Testing Guide
By Haze Games
This guide is here to help you to test the Pre-Alpha version of the game. It includes some known issues, but most importantly some tips on how to test the game efficiently, and contains different shortcuts for Debug Mode that allow you to quickly skip parts or reach specific areas.
 
Rate  
Favorite
Favorited
Unfavorite
Installation
Installing the Pre-Alpha build of Fractal Space is easy:
  • Request a Steam CD Key via email at contact@haze-games.com
  • Create or use an existing Steam account
  • Launch Steam
  • Navigate to Games | Activate a Product on Steam...
  • Copy and paste the CD Key you received by email in the field
  • Click Next
  • Click Accept to agree with the EULA
  • Wait for download to complete
  • Launch the game
You should now have the Haze Games logo, then the game's Main Menu!

Performance
If you are experiencing a low frame rate with the game, or wish to improve performance in general, I recommend you check out the detailed Performance Guide here: https://steamcommunity.com/sharedfiles/filedetails/?id=1502176940
A Wild Error Appears!
The game doesn't crash, but frightening errors appear? Stay calm - here's what you need to do!

Errors in Development Console
While testing, you might encounter code errors. When an error occurs, the game continues to run normally, but the Development Console appears at the bottom left of the screen, and displays them in red, as shown in the screenshot below:


These errors should not happen. We need to make sure they are all fixed, and that the game can be completed entirely without a single code error happening!

Why are they a big deal?
As the game continues to run and doesn't crash, they seem OK... However, they are not! That's mainly because these errors can prevent other code to be executed; meaning you can then have sequences of events which are not executed as they should, and end up with blocking logic bugs, like a door not opening when it's supposed to...

What should I do?
It would be extremely helpful to us, if when you encounter errors like this, you could do the following:
  • Press ESC. to display the PAUSE menu
  • With your mouse, left click the first red error text: this will display more info about it
  • Take a screenshot
  • Send it to us at contact@haze-games.com, or create post in the Bugs Official Steam Forum
  • Try to write in the post/email, a couple of steps you did before this error appeard, and on which platform you are playing
If there are a lot of errors, you can hit ESC. to show the Main Menu and cursor, and scroll up/down to show them all in multiple screenshots. Usually, the first one - the one at the top of the list - is the most important for us

We will then update the game as soon as possible to fix this error for you :)
Thank you very much for your help and cooperation, and have a good code error hunting!
Reset Save Game
If you are encountering major bugs, or if you played with Debug Mode and need to re-test the game in normal conditions, it's best to reset the save game file.

In order to do this, you need to click the ! Reset Save ! button in the main menu or pause menu:

Gamepad Testing
If you have any of the following controllers, it would be great if you could test the game with those:
  • Xbox 360 Controller
  • Xbox One Controller
  • Sony DualShock 4
  • Steam Controller


Testing with a keyboard and mouse is great too, but having feedback and bugs related to controllers is also important to us.

If you find any bugs with the tutorials display, the control system itself, or have any other suggestion to improve the experience, feel free to post in the forums of Bugs or Suggestions :)

In theory, the entire game should be playable with a controller, including all minigames and 2D interfaces. If you encounter any issue with any of those, please report a bug :)

Thank you!
Debug Mode
This part of the guide explains how to use the Debug Mode in the Pre-Alpha build.

First Playthrough
For the first playthrough of Fractal Space, please play normally without ever enabling Debug Mode. Only investigate Debug Mode once you have completely finished the Pre-Alpha, and you require to quickly return to specific areas to take screenshots, videos, reproduce a bug, or if you want to test if a bug is indeed fixed after it's been patched.

Enabling Debug Mode
You can enable Debug Mode in the Main Menu or in-game. It will only display outside cut-scenes. At anytime, enable Debug Mode by pressing on your keyboard the following combination:
  • Shift + F1: Toggle Debug Mode ON / OFF
This will toggle Debug Mode ON / OFF. You can know that Debug Mode is ON because two big arrows at the bottom left and right of the screen appear:

Avoid clicking these buttons with the mouse ;)

Debug Commands
As soon as Debug Mode is enabled, you automatically get the Taser and Jetpack, even if you're not supposed to have it at this point in the game. Below are the available commands while Debug Mode is ON:
  • Numpad +: Skip to Next Checkpoint - Restart Checkpoint required
  • Numpad -: Skip to Previous Checkpoint - Restart Checkpoint required
  • F2: Heal yourself to 100%
  • F3: Fill Taser Energy of 3 shots
  • F4: Toggle Zero-Gravity ON / Off
  • F5: Reset All Upgrades and Upgrade Computers - Restart Checkpoint required
  • F12: Delete All Save Data: You should restart the game after this

Important Warnings
When you skip and find the desired checkpoint, you absolutely need to toggle Debug Mode OFF, and then kill yourself or reload latest checkpoint. If you don't do this, you'll encounter many level design bugs since you're not going through the normal course of a player walkthrough.

The order of checkpoint skipping can sometimes be strange, and you might need to repeat the request to switch to next checkpoint.

Going to previous checkpoint will often bring you back to start of level because checkpoints are destroyed as you progress.

Force Chapter Selection
If you enable Debug Mode while on Main Menu, that shows the CHAPTERS button to start directly from Chapter 2 for example, if you don't have the CHAPTERS button available yet:

Experimental Builds
If you're interested in testing new features in advance, you'll need to access an Experimental Build (a.k.a "EXP builds"). The current Experimental Build only includes Chapter 1.

1. ENABLING EXPERIMENTAL BUILDS
Follow these steps to access the Experimental Build:
  • Open Steam Library
  • Right Click on the game Fractal Space in your Library
  • Click on Properties:

  • In the new Properties window, click on the Beta tab
  • Enter the password fractalexperiment in the Access Code field
  • Click the Check Code button:



You should then be notified that you have access to a new branch:



You can now click on the dropdown list to switch from NONE to experimental:



You can now close the window. The game should start downloading the Experimental Build, and the title in the library should show Fractal Space [experimental]:


Now, you should wait for the download to finish. Meanwhile, please read the section below about testing the new Save System.

2. FIRST LAUNCH
Experimental versions have build names finishing by _exp. Please keep in mind that you may have errors when launching the game due to incompatible previous save games.

The first time you launch the experimental build, you should do the following:
  • Launch the game
  • When the Auto-Save warning is displayed, press TAB to show the Main Menu
  • Click the !Reset Save! button in the Main Menu
  • Click the OK button for the appearing Pre-Alpha popup
  • Click the New Game button

3. TESTING EXPERIMENTAL BUILDS
I recommend you try to record sessions during Experimental Builds, as you may encounter bugs and this will be very useful :)

Thank you very much for your time, support and investment by testing EXP builds!
< >
2 Comments
Haze Games  [author] Apr 25 @ 6:32am 
Just added the "New Save System" section to access Experimental Builds and test the new save system!
Haze Games  [author] Oct 29, 2017 @ 3:11am 
Just added the "A Wild Error Appears!" section tot he guide, to help you with handling a code error that might happen during gameplay. :steamhappy: