CptLoRes

Quick repairs = Manual repair tool and expensive scraps Relatively slow automatic repairs to balance out PvP = Repair unit So all NQ has to do is make the repair unit actually work in a meaningful way. Translation: Maybe some time long after release..

To be fair, the voxel compression in 0.25 seem to have helped with performance. But then again, not having voxel compression up until now in a voxel based MMO is kinda crazy..

Tell me about it. I have a tunnel going into my underground base for ships, and I have spent forever trying to hunt down invisible leftover ground voxels causing havoc.

No

Problem as I see it is that they are not doing either. If you look back over the years comparing release notes with time tables, the progress is abysmal. For example take a look at the more resent 0.23 -> 0.25 progression, consider how many people work at NQ and then look at the features that has been released/improved in what is now closing in on half a years time. A team the size of NQ should be able to work on back-end, fixing bugs and adding features at the same time.

Not sure I follow. This game is already heavily based on physics for flight, so it would be normal to expect the same behavior for other parts of the game. Don't get me wrong, I think DU is way, way to grindy at the moment, but consistency in the game loop is also very important.

Completely agree, but that is the type of functionality that has to been planned for ahead of time and implemented at the core of the game. Key word here being "planned for ahead of time"... sigh.. It is frustrating how old many aspects of this so called next gen mmo is.

This makes me return to one of my old grievances with this game. From a logical and logistical perspective the flying technology in DU does not justify a society where everything flies. Meaning the would have to be something much more efficient for that to make sense.

O man I had forgotten, we have have triangles now! But a release stamp on it, this game is ready! And if I understood the 0.25 release notes correctly, there has been no compression on voxel data until now?!? Well, that explains A LOT..

The only way this extended delay would make any sense, would be if they decided to include some of the more advanced mission types like NPC missions etc. But knowing NQ and despite the long delay. This will probably be some 'early' version of the mission planner with hauling missions only. And the 'early' part of the mission system, like with PvP will remain a long, long time.

No.

Yeah I am gonna necro a bit also, since this thread is a nice window back in time. Looking back at the discussions we had then and what NQ said, the only conclusion I can make is that NQ will say one ting, and do/not do another. Another thing that is striking, is that we can jump years back in time and the discussion is pretty much for the same state of early game that we have today.

Been there, struggled with that. Gave up waiting for a fix and added it to the long list of reasons why I stopped playing DU..

NQ community managers and dev's aren't toddlers, and should be able to separate good from bad ideas. And many of the suggestions has been for glaringly obvious problems. So the main point here is that NQ does hardly ever listened to any feedback, or give any in return for that matter.

Or put in other words. If DU is using GPU for voxels, then why the heck is the game maxing out client CPUs?

Another core feature for most modern voxel engines is GPU acceleration (the voxel matrix math is almost a perfect match), and again this is something NQ does not have. It is amazing how much more powerful a GPU is compared to CPU, provided the problem is a good fit for the GPU architecture. And using modern GPU's the only practical restriction on the amount of voxels shown in a mmo, should be the streaming bandwidth. And using GPU's there should not be a need to meshify constructs for performance (other then bandwidth) reasons. And in my book this is just another one of those "let's just make it work using the quickest and easiest to develop method first, and make it better later" features in DU becoming the permanent solution. And it is disturbing how little actual progress NQ is showing, even using quick and dirty methods. And while NQ is fumbling around, a single person made the tear down game from scratch including the physics based voxel engine in a 2-3 years time frame. Imagine if NQ (68 employees at the moment) had 20-30 people working at that pace.

The list of impressive voxel games/engines is getting longer each day. And all I can conclude is that for a game studio being 100% focused on making a voxel game, NQ is really bad at voxels..

Great idea Gottchar. Only problem is the community has been suggesting variations of that solution for a long, long time, and NQ is completely ignoring it. And they can't even be bothered to tell us why they don't want to implement an effective solution to the district spam that would require minimum dev time.

All you have to do is fly higher then 4km, get a de-sync and fall off. Or if there are other people onboard, the ship will continue for much more then 4km, especially in sub-orbital. Also, any game bug leading to you dying and re spawning away from the ship. Those are just the ones I have experienced, I am sure there are many more.

As long as fetch is needed (why that is, is a whole other discussion), it should at least cover the common scenarios where people need to recover ship due to de-syncs and a slew of other game breaking bugs. And the 4 km limit does not do this, plain and simple.

Mostly the "not doing" part..

And more importantly surrogates was a features reusing existing functionality so they could make it with almost no effort, and still give the impression of progress.

Yes, long loading times is 'normal', especially if you don't have SSD and/or internet connection is marginal. Also go into settings and change to window mode, if you want to alt-tab, resize etc.

[removed image to free up space]

Nope, never was. But I have heard from people who where, that the group was mostly composed of YES people and even then NQ didn't particularly listen very well to that group either, especially if the feedback was negative.