Jump to content

Ninator

Member
  • Posts

    37
  • Joined

  • Last visited

Profile Information

  • Alpha
    No

Recent Profile Visitors

The recent visitors block is disabled and is not being shown to other users.

Ninator's Achievements

  1. Well, subscriptions have run out a week ago. For me personally, DU has shut down. And I am not even feeling sorry.
  2. Things start to make sense. Of course the wipe decision is engraved into the egg. Belorion , share your findings !
  3. Exactly my question : does it make sense to enable it know, or should we wait until wipe happened ? It would be a big advantage to have those bonuses AFTER release ...
  4. When flying with a carpet to collect ore, it's not because of speed. It's because of much better terrain overview. Have an ecu on your carpet, and whenever you see something, just jump off the carpet directly onto the pile of ore. carpet will land safely meanwhile somewhere in front of you.
  5. The only problem now is : Flying with a magic carpet to search all those piles of rock is impossible (inconvenient). Because when you activate the harvest tool to see the rocks, one can no more control the speed of the carpet with the mouse wheel. Already reported as bug. But maybe that will simply not be necessary anymore in the future, because it looks like the rocks are spawning now right under your feet when calibrating...
  6. The current collision algorithm simply seems to be broken: - after the patch many constructs reported overlapping elements, although they were all checked before the patch. - simply moving these elements one tick to the left and back fixed the error. Although the elements went back to the original position, the collision error was gone. That's simply a bug. It happened on multiple ships. How can stuff like that be released ? Where is the QA department ? I thought the patch was tested on PTS ?
  7. So for a while now I am encountering strange air brake behaviour. Sometimes they simply refuse to brake. Like totally. I am approaching my target at 100km/h hovering 20m above the ground, and its like I have no brakes at all. Only when I turn the ship around so I am sliding sidewards, somehow they kick in, and I am able to brake with CTRL again. What can cause this ??? I really do not like to crash into a market with 2 kilo tons of ore because of this. Sombody has an idea ?
  8. Sure. Take a piece of squared paper. We are going to construct some slopes. But the rule is, that voxel edges lay only on the grid of your paper. You can now define the dimension of your voxel ( how many little boxes on your paper make one voxel ). You will see that this choice defines the possible slopes. The definition of the slope is : angle = atan ( dy / dx ) with dx and dy beeing integral (natural) numbers. This boils down to the fact that you can only construct slopes wich use factors from the prime factorization of your voxels dimension. Sounds very mathematical, I know. But you can visualize that with your paper hands on. Of course somebody could now argue : wait a second, I can create much more slopes by (ab)using fractions if i am allowed to move the voxel edges in 2 dimensions. Sure. And the DU engine does that excessively. I personally do not consider those slopes perfect, and they drive me crazy inside the game. Whenever you encounter strange ripples in one dimension when you just changed a slope in another dimension of the voxel , then the slopes are not "perfect".
  9. Addendum to my previous post: There seems to be a confusion with the 252 vs 253 points. 252 is clearly based on the prime factors 2*2*3*3*7 . The 7 seems to be a random choice, and personally if you go that way, I would have factored the 5 also into it. The thing is , if you draw a voxel of width 1.0 on paper and divide it by 10. What you have then is 10 deltas with a spacing of 0.1 and surprise - 11 dots in each dimension. So the amount of dots must always be +1. Otherwise your voxel can not be divided in the middle. Sounds strange, but its like that. The 252 vs 253 sounds like a communication error between the devs and the community managers to me.
  10. Thank you Deckard for explaining it. This clarifies so much. I gave Tordan, the creator of the wonderful voxel wedge a really hard time, because again and again the points in the wedge seemed not to be perfect. We all assumed that the engine representation of a voxel's width was an integer value and a potency of 2. Man, have we been wrong. I deeply need to apologize to Tordan for that. Not his fault. In fact it is simply mathematically impossible to create a perfect 1/8 or 1/16 wedge with that numerical system. All I can do at this point is to slowly walk away from this numerical nonsense. I am sorry. But from a coders perspective, I simply can not trust the team anymore. Edit : My statements needs more explanation. So someone could actually argue that it makes sense to have as many prime number deviders as possible in the width of a voxel in order to be able to create certain perfect slopes ... Unfortunately the team that coded the available rotation angles for elements did not talk to the voxel team. Everybody who ever created a perfect slope in a cockpit and tried to align glas windows to it knows what I am talking about. It's a mess...
  11. this is failing due to several reasons. did you ever try to put down a static core on an asteroid ? it says "no territory". putting down a space core does not help either, because it can be shot. sorry ... But : as a hint : your space suit is quite capable of flying some su if you are patient ...
  12. and there my friend, I am sorry to tell you, you are wrong. It is all about psychology. There is a huge difference between - if you define the base yield at 100% and punish the player when he is not calibrating versus - if you calibrate nicely, you are rewarded and get more than 100%. see the difference ? Its called motivation. All game loops should be designed to be motivating. If they are not, the game designer failed.
  13. there is no obstruction for weapon damage so far, which is silly.
  14. as Deckard said : it happended and they realized the mistake.
  15. Guys, the problem is a technical one and quite simple : - Demeter patch hit everybody at the same time. - So tax bill must be issued for the whole player base at the very same time. - This means a permanent stressful server overload every week at the very same time. It is very much preferable from a server perspective, if he can deal with taxes one after the other with some pause inbetween. No big deal. What is really surprising is the fact, that the developer who designed that , did not think about it. Its a classic problem ...
×
×
  • Create New...