Projectors using more PCU then intended after Wastelands Update

The blueprint file provided has the issue which was newly made, It will display in Info tab that it only takes 65 PCU when projecting but in G menu it Uses Built PCU amount and once Fully Built it uses Double PCU Cost Even though in Info Tab it displays incorrect info, This is a really counter intuitive bug for building on Official servers as pcu is already low as is and having it lowered double the amount from a projection Which in fact was not an issue Before the recent update as a Projection each block would only Cost 1PCU depending on projection size. See Attachments Se bug # 3 - 4 - 5 - 6. I included the Blocks, it can be any PCU intensive block that Does it. I am unable to Provide a Save currently as the bug was Discovered on an official Keen Server But it can be easily replicated on worlds.

here is the same Attachement of Pictures in order Prior to Wasteland update. Easy to notice a big PCU usage Difference between Both. i Used the same Projector PCU Bug Blueprint for this test as well

The Second and Third Images - "Se Bug 4.png" "Se Bug 5.png" and "Se bug before Wastelands 2" And "Se bug before Wastelands 3" Are the Big noticeable differences. In PCU usage. I'm surprised nobody else has noticed this

The Save used to provide visible Test is this one. And it is the same for the Wasteland update.

Hello,

Thank you for providing the information. I'm afraid I haven't been able to replicate this issue as the projection is showing as costing 25 PCU please find attached my screenshots.

If you haven't tried the following, this may help your issue -

• Verify your game files in Steam

• Right click on Space Engineers in Steam Library → Properties → Local Files → Verify Integrity of Game Files

• Delete SpaceEngineers.cfg file

• It means your game configuration will be deleted
• You can access your SpaceEngineers.cfg by typing %appdata% into your Windows search bar and you will be redirected to the hidden Roaming folder. After that just follow: \Roaming\SpaceEngineers.

• Delete ShaderCache folder

• Same access as SpaceEngineers.cfg

• Back up your whole Space Engineers Roaming folder and delete it
• Restart Steam
• Reinstall VC Redist 2017
• Update graphic drivers
• Reinstall the game
• Make sure your operating system is fully updated

I hope this helps you.

Kind regards,

Thank you for the Reply

Followed all 8 Steps

Did not resolve my issue problem. If i revert the space engineers to prior the 2nd Hotfix after Wasteland update The issue Does not happen. This problem resides in the recent Hotfix that was released After Wasteland update.

Unfortunatly it does not fix the issue as others i play with have the same issue on Official servers as well

Hello,

Thank you for trying these steps and I'm sorry this has not fixed your issue. Is it possible that you could provide reproduction steps and a video if you are able to do so? This would be a great help to try and reproduce the issue you are having.

Kind regards,

Version 1.197.065

Reproduction Steps

1. Create new World
2. Fully Build PCU intensive block/s
3. Create new Blueprint of Blocks (Ctrl-B)
4. Remove PCU intensive Blocks
5. Build projector and Power source
6. Check PCU usage in G menu (Bottom right corner)
7. Input newly created blueprint
8. Check PCU use in G menu (Bottom right corner)
   I have reason to believe this bug is related to Phantom Grids, A grid which does not physically exist but takes up PCU as a Projection Grid which count as built grids when projected.

https://drive.google.com/file/d/16U0OVx5aiXVKqBoFMdIDVafqKvNs_OvP/view?usp=sharing

Following Harley's steps, I can project a gatling turret with a projector and battery and the projected gat turret shows in my info panel and uses the full PCU as pictured - This has greatly damaged playability on our server.

Deleting the gatling turret from the info panel results in a crash to desktop with error "Exception occurred: System.NullReferenceException: Object reference not set to an instance of an object. at Sandbox.Game.Entities.MyCubeGrid.RemoveBlock(MySlimBlock block, Boolean updatePhysics)"

Adding too this, the doubling projector only occurs when the blueprint is blueprinted in survival. That's why blueprinting in creative fixes it. (From the experience had and what others have said in the server am apart of)

If you didn't ahh realise, that's a month.

Hey,

I am still getting this issue.

It looks like when i am trying to put a projection over a ship i am trying to fix, the more the projection is over the ship, the more in the negative pcu i go