JayleBreak

Be careful what you wish for.

NQ: please introduce a new type of radar with a detection range of constructs that have weapon elements to say... 10su. The new radar should be considered a weapon as well. There should be no objection to PvP enthusiasts being able to find each other to fight.

All terrain within the boundaries of a static construct should be converted (on core placement) to normal voxels with terrain material types. Thus all voxel tools (copy, paste, delete, smooth etc.) could be used to landscape the build.

All terrain within the boundaries of a static construct should be converted (on core placement) to normal voxels with terrain material types. Thus all voxel tools (copy, paste, delete, smooth etc.) could be used to landscape the build.

Merry Christmas and Happy New Year 2023
-k-

NQ: please introduce a new type of radar with a detection range of constructs that have weapon elements to say... 10su. The new radar should be considered a weapon as well. There should be no objection to PvP enthusiasts being able to find each other to fight.

They should have assigned a shift click deployment key to pop-up the virtual scaffolding dialog box (I'd accept a wireframe of the construct too if needed) with initial values (scale would be fixed to 1) set to the deployment settings. That would allow precise placement and rotation. There would still be some tedium in getting the desired alignment but it would at least be straight forward.

I always find it amusing when 'pirates' in this game talk about the need for others to face challenges while taking part in maybe the least challenging 'pvp' activity in all of gaming.  I don't put the blame on any particular group. It is all down to sht game design. 
 
If it wasn't for asteroids outside the safe zone, pvp game play would be almost pointless so giving the OP his wish would result in the destruction of the gameplay loop others enjoy.  Which hardly seems fair.  So once again, the fault is with NQ which is unable to implement pvp in any way that doesn't resemble big game hunting at a zoo. 

You go there. I didn't start playing this game for PVP. 

For me, on Windows 10, I found it by
Click "Start" menu button Select "Settings". Select "Power & sleep". On the right hand side, under "Related settings" click: "Additional power settings." Under "Preferred plans" click on "Change plan settings" for the plan your PC is using. Click  "Change advanced power settings". You should now see the pop-up in the picture above (in your active language setting). Continuing: Expand "Processor power management." Expand "Maximum processor state." Click on the "100%" link and set it to 99. Thanks to VanDamage for pointing this out.

For me, on Windows 10, I found it by
Click "Start" menu button Select "Settings". Select "Power & sleep". On the right hand side, under "Related settings" click: "Additional power settings." Under "Preferred plans" click on "Change plan settings" for the plan your PC is using. Click  "Change advanced power settings". You should now see the pop-up in the picture above (in your active language setting). Continuing: Expand "Processor power management." Expand "Maximum processor state." Click on the "100%" link and set it to 99. Thanks to VanDamage for pointing this out.

With the return of element lifetimes the development of Lua flight scripts (e.g. flying_construct.conf) carries the risk of excessive costs.

The solution would be to provide a VR environment similar to that in the "Challenges" tab of the Surrogate Pod UI, but where the ships have no DRM restrictions on their controllers. The code loaded into those controllers should not be saved to the server, but copy & paste should be permitted. Loading of configuration from the lua/autoconf/custom folder should be allowed.

Offering a variety of ships would be great and if a variety of elements (radars, guns etc.) were available to modify the ships it would magnify the development possibilities.

With the return of element lifetimes the development of Lua flight scripts (e.g. flying_construct.conf) carries the risk of excessive costs.

The solution would be to provide a VR environment similar to that in the "Challenges" tab of the Surrogate Pod UI, but where the ships have no DRM restrictions on their controllers. The code loaded into those controllers should not be saved to the server, but copy & paste should be permitted. Loading of configuration from the lua/autoconf/custom folder should be allowed.

Offering a variety of ships would be great and if a variety of elements (radars, guns etc.) were available to modify the ships it would magnify the development possibilities.

With the return of element lifetimes the development of Lua flight scripts (e.g. flying_construct.conf) carries the risk of excessive costs.

The solution would be to provide a VR environment similar to that in the "Challenges" tab of the Surrogate Pod UI, but where the ships have no DRM restrictions on their controllers. The code loaded into those controllers should not be saved to the server, but copy & paste should be permitted. Loading of configuration from the lua/autoconf/custom folder should be allowed.

Offering a variety of ships would be great and if a variety of elements (radars, guns etc.) were available to modify the ships it would magnify the development possibilities.

With the return of element lifetimes the development of Lua flight scripts (e.g. flying_construct.conf) carries the risk of excessive costs.

The solution would be to provide a VR environment similar to that in the "Challenges" tab of the Surrogate Pod UI, but where the ships have no DRM restrictions on their controllers. The code loaded into those controllers should not be saved to the server, but copy & paste should be permitted. Loading of configuration from the lua/autoconf/custom folder should be allowed.

Offering a variety of ships would be great and if a variety of elements (radars, guns etc.) were available to modify the ships it would magnify the development possibilities.

With the return of element lifetimes the development of Lua flight scripts (e.g. flying_construct.conf) carries the risk of excessive costs.

The solution would be to provide a VR environment similar to that in the "Challenges" tab of the Surrogate Pod UI, but where the ships have no DRM restrictions on their controllers. The code loaded into those controllers should not be saved to the server, but copy & paste should be permitted. Loading of configuration from the lua/autoconf/custom folder should be allowed.

Offering a variety of ships would be great and if a variety of elements (radars, guns etc.) were available to modify the ships it would magnify the development possibilities.

With the return of element lifetimes the development of Lua flight scripts (e.g. flying_construct.conf) carries the risk of excessive costs.

The solution would be to provide a VR environment similar to that in the "Challenges" tab of the Surrogate Pod UI, but where the ships have no DRM restrictions on their controllers. The code loaded into those controllers should not be saved to the server, but copy & paste should be permitted. Loading of configuration from the lua/autoconf/custom folder should be allowed.

Offering a variety of ships would be great and if a variety of elements (radars, guns etc.) were available to modify the ships it would magnify the development possibilities.

With the return of element lifetimes the development of Lua flight scripts (e.g. flying_construct.conf) carries the risk of excessive costs.

The solution would be to provide a VR environment similar to that in the "Challenges" tab of the Surrogate Pod UI, but where the ships have no DRM restrictions on their controllers. The code loaded into those controllers should not be saved to the server, but copy & paste should be permitted. Loading of configuration from the lua/autoconf/custom folder should be allowed.

Offering a variety of ships would be great and if a variety of elements (radars, guns etc.) were available to modify the ships it would magnify the development possibilities.

Koruzarius from discord posted that they have done just this. You can VR to TRNU Starter Samples
It has starter crafts and starter houses.

I was really looking forward to the new planets and thought the Beta wipe was going to be when they would introduce it. It wasn't and I forgot about it, but maybe we should ask Aphelia if the changes have been dusted off and completed or was it all a mirage?

Looking at the problem statement: "Too many people building everything without involving others", why does NQ (and a lot of players) equate that with a problem with industry that needs fixing (one way or another).

Focus on making it easier for people to buy instead of making things harder to build. My suggestions are:
Make all markets on a planet have the same buy and sell orders (e.g. place Market 6 terminals in every marketplace on Alioth and get rid of the local terminals).  Distribute markets around planets so every territory is close to a market. I like how Haven was set up (may have added a few more markets though). Change the nano-crafter so any item it can make can alternatively be instantly bought from the planetary market (if being sold by a player) and placed in your inventory (same as if it had been crafted). Remember, its consumer spending that drives economies not manufacturing. 

Looking at the problem statement: "Too many people building everything without involving others", why does NQ (and a lot of players) equate that with a problem with industry that needs fixing (one way or another).

Focus on making it easier for people to buy instead of making things harder to build. My suggestions are:
Make all markets on a planet have the same buy and sell orders (e.g. place Market 6 terminals in every marketplace on Alioth and get rid of the local terminals).  Distribute markets around planets so every territory is close to a market. I like how Haven was set up (may have added a few more markets though). Change the nano-crafter so any item it can make can alternatively be instantly bought from the planetary market (if being sold by a player) and placed in your inventory (same as if it had been crafted). Remember, its consumer spending that drives economies not manufacturing. 

If you are going to do a wipe prior to release then do it right:
Grandfather all those who have been subscribed to Beta for 3 months or more into the alpha program at a level commensurate the length of time they subscribed  (i.e. give them DACs) Give everyone eligible for DACs  or who preorders the release a starting pool of talent points (e.g.  30days worth of training). Preserve blueprints. Note: in practice most are obsolete or require a lot (months) of resources & industry development before they can be used. FIX the ECONOMY! A wipe will NOT do that by itself. I suggest: Have all marketplaces on a given planet or moon reference the same pool of buy/sale orders. Sale orders can be created at any marketplace like today. Buy orders can be fullfilled anywhere on the planet (no flying back and forth just to get an item which can be crafted locally faster). Perhaps a new kind of dispenser could be created for use in static constructs.

If you are going to do a wipe prior to release then do it right:
Grandfather all those who have been subscribed to Beta for 3 months or more into the alpha program at a level commensurate the length of time they subscribed  (i.e. give them DACs) Give everyone eligible for DACs  or who preorders the release a starting pool of talent points (e.g.  30days worth of training). Preserve blueprints. Note: in practice most are obsolete or require a lot (months) of resources & industry development before they can be used. FIX the ECONOMY! A wipe will NOT do that by itself. I suggest: Have all marketplaces on a given planet or moon reference the same pool of buy/sale orders. Sale orders can be created at any marketplace like today. Buy orders can be fullfilled anywhere on the planet (no flying back and forth just to get an item which can be crafted locally faster). Perhaps a new kind of dispenser could be created for use in static constructs.

They never said what the maximum time is - they should have. 18 hours is the minimum time (its in your quote from the devblog) and they didn't say what determined the actual time which would also be nice to know.