Mucus

Do you really think that a completely random mining calibration mini game grind is FUN ?
 
 
Why, if this was a performance improvement do we still get pending ops when transforming the surface?
 
 

Do you really think that a completely random mining calibration mini game grind is FUN ?
 
 
Why, if this was a performance improvement do we still get pending ops when transforming the surface?
 
 

Do you really think that a completely random mining calibration mini game grind is FUN ?
 
 
Why, if this was a performance improvement do we still get pending ops when transforming the surface?
 
 

Do you really think that a completely random mining calibration mini game grind is FUN ?
 
 
Why, if this was a performance improvement do we still get pending ops when transforming the surface?
 
 

Do you really think that a completely random mining calibration mini game grind is FUN ?
 
 
Why, if this was a performance improvement do we still get pending ops when transforming the surface?
 
 

Kinda split on removing old scan data seeing as how it was mentioned that folks would be keeping them in the recent Q/A video. Yeah it will be another land rush and all, I just wonder how many people won't be participating this time around.
 
I'm all for it but man, these last minute changes are killing us.
 
Also...
I'm not good at math, but do you mean two mining units? 50+50=100, I'm not sure where 'four' is coming from. Maybe yall are working with 50% efficiency?

.......... ..

.......... ..

In addition to Evilteks point re: feedback , NQ, please test it properly before you release by building ships and checking that elements can be placed and don't collide outside their visible shapes. Don't assume it works test it thoroughly.
 

In addition to Evilteks point re: feedback , NQ, please test it properly before you release by building ships and checking that elements can be placed and don't collide outside their visible shapes. Don't assume it works test it thoroughly.
 

Yea I hope that we could get a player camera rotation directions as well as camera type (1-st/3-rd person)

I would very much like to believe that, but the circumstances of Hello Games and Novaquark were quite different.
By the time Hello Games started working on NMS, they had already shipped 3 games, so it's not too much of stretch to say they have had a small, but fairly experienced team to work with. Most of the launch troubles of NMS were due to not having experience working on project of that magnitude, consequently falling behind the production schedule,  which led to having to choose between releasing what they had at the time or go bust.
 
In Novaquark's case it's a team that has never realeased a commercial title, led by someone who had no experience making any game indie, hobbyst or commercial.  To make things even more complicated, they decided to license a rather obscure game engine with no proven track record, besides a few simulations and couple of obscure games that have not even been released at the time.  Add a rather play it by the ear approach to design, NQ setup really has Sisyphean quality to it. 
 
If you think about it, with the way they stacked their own deck, it's quite a miracle NQ managed to release anything at all.  Like quite a few of you i did enjoy DU for a while but at some point i realized DU really is as wide as an ocean and as shallow as a pond. And it's hard for me to see it changing with NQ's  unique talent of spending incomprehensible large share of their time digging themselves out of countless holes, instead of spending a little extra time on avoiding jumping into those very holes in the first place.

It is kinda telling when this forum as sad as it is, is giving me more entertainment then playing the game.

Could we get the option to stop the general chat notifications? Because I couldn't really care less what's going on in that channel, never have.

I agree. You just have to look at the implementation of a command chair and the avatar slouch(Abrams star trek JT Kirk copy) position and the fact that you still can' t align the position of your cross-hair central to the voxels of your construct design.  Perhaps an option to center cross-hair would be in order also. 
 
Differentiation is one thing stupidity is another.
 
 

I agree. You just have to look at the implementation of a command chair and the avatar slouch(Abrams star trek JT Kirk copy) position and the fact that you still can' t align the position of your cross-hair central to the voxels of your construct design.  Perhaps an option to center cross-hair would be in order also. 
 
Differentiation is one thing stupidity is another.
 
 

Back in Alpha the external view for all chair units was focused directly on the players character, something like this:

 
This was great. You would spend weeks building a ship and then fly for a few hours to another planet (before warp), but it was OK, because with the camera pointed directly at your character you could zoom in/out/through the ship and view it from any angle. This was perfect for taking screenshots of your ships in flight, you could get close ups directly in front of the cockpit, or behind the engine stacks, etc. I would post some Alpha examples, but that's not allowed ?
 
With the introduction of PvP NQ decided to change this external view and give the current 'periscope' view instead:

 
Now, the camera is directly above the construct, and as you zoom in the construct disappears from your view. There is no way to zoom in directly on your character/chair. (Unless I'm missing some hidden keybind??)
 
I had assumed that with the new Chair Surface NQ would have implemented a view similar to the old Alpha chair views, where the zoom is focused on the character. Unfortunately, the external view is just a copy/paste of the periscope view ?‍♂️
 
If you put a Chair Surface on an L Static, you get a camera way up in the air above the center of the construct, with no relation to the position of the Chair Surface, and no way to zoom in on your character. 
 
This is such a bad implementation ?
 
The original Alpha external camera zoom view would be so much better, and would allow you to place Chair Surfaces in different locations, so ppl could zoom in on different sections of the construct to admire the building work.
 
1) Please NQ, add an option to change the zoom view on Chair Surfaces to the old Alpha style zoom, so we can actually use them to view constructs, rather than some nebulous empty space in the air above them.
 
and, more importantly...
2) PLEASE also add an option to change to the Alpha zoom view to all other chairs, (Command Chair, Hovercraft Seat, etc.). Not everyone PvPs and needs the 'periscope' view. As a ship builder I really want to be able to view my actual ship while flying it, and zoom in/through to my character. This would increase the enjoyment of ship building/flying no end.
 
It would probably take someone a couple of hours to implement, heck, you probably still have the old code in there somewhere
 
 

They've clearly abandoned their users. My guess is they're looking for a buyer for the tech and they'll be closing the game down soon. They just aren't acting like they intend to build a game anymore.

Purpose,  Makes lights randomly change rgb colour and cycles them to give a breathing effect.
 
Level:
Lua  beginner = cut and paste code, create filters unit start and system update in lua editor , DU = know how to link lights to a programming board
Build
You need 1 Programming Board(PB) and some lights. Connect the lights to the PB and name each slot in the lua editor (Ctrl L) you have connected l1 , l2 etc. If you don't want 8 then edit the source code and remove. 
code is below.
 
Other stuff you can do : add a detector to autostart ,  change parameters in unit start to get the feel you like.
 
-- copy and paste into unit start
 
unit.hide() -- hides programming board
-- remove these where you have not connected a light
l1.activate()
l2.activate()
l3.activate()
l4.activate()
l5.activate()
l6.activate()
l7.activate()
l8.activate()
bClock          = system.getTime() -- start clock
origRgb         = l1.getRGBColor() -- stores the colour of the original light if you want to reset lights on exit
breathRate      = 1 --export: rate of breathing Multiplier
changeFrame     = 1200 --export: frame colour and channel cycle
rgbIndex        = utils.round(math.random(3)) -- choose channel to breathe
r               = math.random(255) -- setup channels
g               = math.random(255)
b               = math.random(255)
frameCount      = 0
 
-- Copy and Paste into System update
frameCount = frameCount + 1
 
if ( frameCount % changeFrame == 0 ) then --randomize rgb and channel
    r = math.random(255)
    g = math.random(255)
    b = math.random(255)
    rgbIndex = utils.round(math.random(3)) -- choose channel to breathe
end
nClock = system.getTime()
local timeSeconds = ( nClock - bClock)
local breath = utils.round(( math.exp( math.sin(timeSeconds * breathRate )) - 0.36787944 )* 108.0)
 
if rgbIndex == 1 then
    r = breath
    elseif rgbIndex == 2 then
    g = breath
    else
    b = breath
end 
-- set rgb colour of linked lights ,remove these where you have not connected a light
    l1.setRGBColor(r,g,b) 
    l2.setRGBColor(r,g,b) 
    l3.setRGBColor(r,g,b) 
    l4.setRGBColor(r,g,b) 
    l5.setRGBColor(r,g,b) 
    l6.setRGBColor(r,g,b) 
    l7.setRGBColor(r,g,b) 
    l8.setRGBColor(r,g,b) 
 

Purpose,  Makes lights randomly change rgb colour and cycles them to give a breathing effect.
 
Level:
Lua  beginner = cut and paste code, create filters unit start and system update in lua editor , DU = know how to link lights to a programming board
Build
You need 1 Programming Board(PB) and some lights. Connect the lights to the PB and name each slot in the lua editor (Ctrl L) you have connected l1 , l2 etc. If you don't want 8 then edit the source code and remove. 
code is below.
 
Other stuff you can do : add a detector to autostart ,  change parameters in unit start to get the feel you like.
 
-- copy and paste into unit start
 
unit.hide() -- hides programming board
-- remove these where you have not connected a light
l1.activate()
l2.activate()
l3.activate()
l4.activate()
l5.activate()
l6.activate()
l7.activate()
l8.activate()
bClock          = system.getTime() -- start clock
origRgb         = l1.getRGBColor() -- stores the colour of the original light if you want to reset lights on exit
breathRate      = 1 --export: rate of breathing Multiplier
changeFrame     = 1200 --export: frame colour and channel cycle
rgbIndex        = utils.round(math.random(3)) -- choose channel to breathe
r               = math.random(255) -- setup channels
g               = math.random(255)
b               = math.random(255)
frameCount      = 0
 
-- Copy and Paste into System update
frameCount = frameCount + 1
 
if ( frameCount % changeFrame == 0 ) then --randomize rgb and channel
    r = math.random(255)
    g = math.random(255)
    b = math.random(255)
    rgbIndex = utils.round(math.random(3)) -- choose channel to breathe
end
nClock = system.getTime()
local timeSeconds = ( nClock - bClock)
local breath = utils.round(( math.exp( math.sin(timeSeconds * breathRate )) - 0.36787944 )* 108.0)
 
if rgbIndex == 1 then
    r = breath
    elseif rgbIndex == 2 then
    g = breath
    else
    b = breath
end 
-- set rgb colour of linked lights ,remove these where you have not connected a light
    l1.setRGBColor(r,g,b) 
    l2.setRGBColor(r,g,b) 
    l3.setRGBColor(r,g,b) 
    l4.setRGBColor(r,g,b) 
    l5.setRGBColor(r,g,b) 
    l6.setRGBColor(r,g,b) 
    l7.setRGBColor(r,g,b) 
    l8.setRGBColor(r,g,b) 
 

Perhaps it would make more sense if schematics were uncoupled from quanta and gained either by traveling somewhere  to get them , researching them or through quests. There could even be a research technology industry unit.

Perhaps it would make more sense if schematics were uncoupled from quanta and gained either by traveling somewhere  to get them , researching them or through quests. There could even be a research technology industry unit.

Perhaps it would make more sense if schematics were uncoupled from quanta and gained either by traveling somewhere  to get them , researching them or through quests. There could even be a research technology industry unit.

Sure hope I recoup some of the 550 million i spent on schematics then. If not I'll be done. Nobody likes wasted time and it seems that's all NQ is doing with my time and efforts to "play the way they intend the game to be played".

I completely disagree. Since most crashes are caused by bugs - at least for me... maybe the rest of you are sloppy pilots - we shouldn't be penalized for that.
 
Overall, the proposed changes look good.
 
I'm also not convinced that feedback from ATV hasn't hurt the game more than helped it.