Sign up Calendar Latest Topics

  Author   Comment  

Posts: 51
Reply with quote  #1 
SE is get ing bigger and bigger, and eventualy we will have planets.  if you would imagine the size of a planet compaired to a fliping large asteroid, you know we need some performance changes vary soon.

Posts: 136
Reply with quote  #2 
i somewhat doubt that, given planets were added, you could fly from planet to space without any kind of loading screen when enetering / leaving the atmospehere.
so you're basically loading another world, consisting of a sh!tload of asteroid, which currently would melt your PC. a chunk system would make that a lot smoother, since you wouldn't load the entire planet, but just the area around you. and the chunk system could be used for the regular space aswell: massively reducing the neccessary "Map-size" you currently have to (down)load, every time you join a server.

Avatar / Picture

Posts: 155
Reply with quote  #3 
I don't think they'll add another loading screen. They'll likely heavily optimize planets so it won't bring down some of our not-so-powerful-computers.

Posts: 4,787
Reply with quote  #4 
A planet is not larger than a large asteroid. it's just one of those with a skybox behind it which occasionally also gets rendered [wink]

Posts: 51
Reply with quote  #5 
OK ATTENTION!!!:  I was just now playing SE and was still laging.  so i set the view distance to "low end machines" and decreaced max obj. by 600+.  Still lags...  I only have one large asteroid, 4 small ones that are potato shaped, my large ship which i made from the yellow pod ship (its two pods long), and and two halvs of a business shipment...  (the back half is floating awat slowly)

WHY CANT WE FIX THIS NOW?! [comp]  [comp]  [comp]
My system information:


Operating System: Windows 7 Home Premium 64-bit (6.1, Build 7601) Service Pack 1 (7601.win7sp1_gdr.150202-1526)

Language: English (Regional Setting: English)

System Manufacturer: LENOVO

System Model: IdeaCentre K430


Processor: Intel(R) Core(TM) i7-3770 CPU @ 3.40GHz (8 CPUs), ~3.4GHz

Memory: 16384MB RAM

Available OS Memory: 16346MB RAM

DirectX Version: DirectX 11

User DPI Setting: Using System DPI

System DPI Setting: 96 DPI (100 percent)

DWM DPI Scaling: Disabled

DxDiag Version: 6.01.7601.17514 32bit Unicode


Display Devices


Card name: AMD Radeon HD 7800 Series

Manufacturer: Advanced Micro Devices, Inc.

Chip type: AMD Radeon Graphics Processor (0x6819)

DAC type: Internal DAC(400MHz)

Device Key: Enum\PCI\VEN_1002&DEV_6819&SUBSYS_E221174B&REV_00

Display Memory: 4095 MB

Dedicated Memory: 997 MB

Shared Memory: 3098 MB


Posts: 58
Reply with quote  #6 
Why can't we fix this now?

I know no-one wants to read this again, but:
It is because this game is in early-alpha, and fixing it now would defeat the purpose of the alpha stage of development.

Do your research when you buy an early access game. This game is not done, and never pretended to be.

In alpha you add in features, making it so that they work... sort of. This doesn't mean bugs won't get fixed, but it's not a priority, because any bug you might fix will likely get bugged again later when you add in yet another new feature. For this reason, it's more productive to keep the product in a barely working condition in this stage, because bug-fixing is more than likely going to be undone again in later stages of alpha.

In beta you optimise and fix. Making sure that the features that were added in alpha get better performance, and that the product runs at better framerates. You also squash bugs at this stage. This doesn't mean features won't be added at all, but the focus is on optimisation and bug-fixing.

Finally, you release. In theory as bug-free as possible.

Post-release updates: Anything you add after that needs to go through the entire chain of adding a new feature, optimisation and fixing and finally release.

Optimising before all features are in doesn't work very well, because new features often bug out older ones, rendering the work done on any bugfixing useless. For this reason, you add as many features as possible BEFORE optimisation and bug-fixing. Because anything that gets added AFTERWARDS is going to take much longer to implement, because it has to be bug-fixed right away; yet it might also break parts of the game you already fixed, rendering previous work undone.

KSH keeps this game somewhat playable, because it profits from a playable alpha. This doesn't change the fact that it's still an alpha. For example, they settled to ABANDON the current multiplayer code in favour of a better one that also supports Xbox-Live (Marek's februari blog post), so it needs to get rid of Steam-dependancies. And people still expect full support and bugfixing on a part of the game that's scheduled to be fully replaced by new code. I don't have to tell you that that's a ridiculous expectation.

The first bits of optimisation are in the works (see Marek's februari blog-post, specifically the bits about DX11 and LOD and multi-threading). Be patient. This isn't a bad game, you just bought it as an EARLY ACCESS. While you should have done some research on what that means, the good news is that if it's unbearable to you, you can just drop it for a few months and see how it's ended up after that little break. It might be worse, but it could also be better. The bad news is that for now, all you can do is be patient. They ARE working on it, but bug-fixing before all major gameplay features are in is a major risk of a lot of dev-time being wasted if stuff keeps breaking with every new feature.

Bottom line, just be patient. This is supposed to happen.

Posts: 51
Reply with quote  #7 
Ok you have a vary good point indeed.  Reguardless of what happons, it is only in alpha.  hahaha!  So ok bug fixes can wait.   

  Thanks KSH for this wonderful game!
Previous Topic | Next Topic

Quick Navigation:

Create your own forum with Website Toolbox!