Install Steam
login
|
language
简体中文 (Simplified Chinese)
繁體中文 (Traditional Chinese)
日本語 (Japanese)
한국어 (Korean)
ไทย (Thai)
Български (Bulgarian)
Čeština (Czech)
Dansk (Danish)
Deutsch (German)
Español - España (Spanish - Spain)
Español - Latinoamérica (Spanish - Latin America)
Ελληνικά (Greek)
Français (French)
Italiano (Italian)
Bahasa Indonesia (Indonesian)
Magyar (Hungarian)
Nederlands (Dutch)
Norsk (Norwegian)
Polski (Polish)
Português (Portuguese - Portugal)
Português - Brasil (Portuguese - Brazil)
Română (Romanian)
Русский (Russian)
Suomi (Finnish)
Svenska (Swedish)
Türkçe (Turkish)
Tiếng Việt (Vietnamese)
Українська (Ukrainian)
Report a translation problem
It would be too much work to adjuste anything only to be more balanced.
I only want to play. I will still use the mod as it is.
The suggestions you made would certainly be useful but they would need to be made at the ToolCore level rather than in this mod. I'm not certain if / when the TC dev plans on adding more functionality to the framework though.
Space Engineers Q Tech Beam Drill
https://youtu.be/G-eVJw65UFc
So, I apologise for giving the wrong information based on my set up. Your drill beam should be a fundamental part of the begging stage of the game, it is a sucker for power but worth it. At the end I switch to the mod DrillSystem because it is far flexible.
Two things I would do to improve this wonderful drill, an auto cut of when no more ore can be dig out (saving power) also a visual queue such as a progression strip/bar or numeric 0 (current dig)/25m (max range), if the visual would be a pain to implement, then the cut off will do.
I will make a video showcasing how it works.
Thanks.
The single bit of indeterminate weirdness aside, this mod is fantastic!
1. A change in TC that has broken something (I'm not aware of any changes though).
2. A mod conflict.
3. A corrupted mod download.
4. A corrupted world save.
5. Some random Keen change that no one has figured on yet.
There are issues with the TC drills as well so I'm busy looking at them (in slow time as I don't have a lot of time to dedicate to this right now) to see if I can figure out what's wrong.
As for BnR not working, I can't speak to why that might be. My best guess would be a mod conflict between the script running BnR and the script running ToolCore. If they are incompatible then you'd need to reach out to the mod authors to find out why.
I wish there was something I could do to fix this but I suspect not even Keen could do that. Tools like these are entirely at the mercy of the framework that controls them (which is itself a 3rd party script so caveat emptor and all that) and then Keen's API and game on top of that.
For the drive units, the red is the back where the thrust "would normally" come out; hence the red colour. I should probably include that in the guide. I think there's also a red "light" on top near the front indicating it's the front but I accept it's probably not the most intuitive way of doing it.
The small thruster (red/blue) should have a way to know what directioin is the thrust.
This is issue isn't limited to just this mod, nor does it affect others. I am absolutely baffled, and cannot find the answer elsewhere... 'Help me Obi-Won Kanobi. You're my only hope.'
Turns out that it was other scripts running in Programmable Blocks that were actually the root cause, not TC. Apparently Keen puts no limit on how much memory a PB is allowed to consume and so some badly written scripts (think ChatGPT) turned out to be the cause.
Not saying that's your issue, but I would check it off as a possibility at least. The devs and other modders are pretty certain after a month's worth of back and forth that TC doesn't have a mempry leak.
If your issue persists then the best thing to do is go to the Discord for WeaponCore with the exact steps to reproduce the issue along with logs showing the leak and hand it over to the TC devs.
I'll ask around and see if the TC dev is aware of the memory leak and if she has a fix in the pipeline.
@Qarannia
When I tested and started a new game, I only started it with a single mod. I only have the "Q-Tech Utilities 3.6" the copied and changed version with AppData \ Roaming
Everything is going well, no problems. You can change it as much as you want. No problems. But as soon as other mods come, it causes problems.
I don't want to take your time anymore. This is somehow embarrassed to me. You helped me so much. When a game stops being a game and becomes a work, it is no longer fun. I have enough stress in real life. I don't have to have that in the game either. Maybe I'll play again later.
Thanks for your time and help.
When you created a fresh world did you put only the locally modified mod in or did you put other mods in as well? Only reason I ask is that I don't get errors like that with my game.
@Qarannia (Thanks)
After a lot of trying and testing I found out that there are mod conflicts. One of them is "AQD - Conveyor Expansion" when I removed this mod I got a different error message.
Unfortunately, this error message does not tell you which mod it is. I don't understand it. What does an "AQD - Conveyor Expansion" system have to do with Crago storage?
It adds new conveyor belts. I have over 100 mods, which means I have to test every single one. It's a lifetime of work.
A game should be fun, not work. I already have enough stress in life. This game makes you even more work. That's really sad.
It doesn't change even if you start a new game.
See You
@Qarannia
Thank you for taking the extra time to help me. I will work through the list when I have time for it. I can tick off the first point, I only have one version of this mod in my mod list, which I copied over to the AppData\Roaming folder.
I don't understand why Space Engineers is so reluctant to accept this small change in the amount of memory. It's very deceptive of Space Engineers. Unfortunately, it spoils the fun of the game. You want to play something on your own to forget about everyday life, and then something like this happens.
See You.
1. You're not running both versions of the mod in your world save.
2. Check for any errors in the XML file you edited. You may want to check on Keen's Discord if there are any limits to how large you can make those cargo hold volume numbers. I'm not aware of any limits but there may be. It's possible you're trying to make it too big. You could try starting by making the volume only a bit bigger to see if that works.
3. Check that it's not something else causing that error. Try making a fresh world save with only that local mod to see if it still gives the error.
I followed the instructions exactly. Local files are located in AppData\Roaming\Space Engineers\Mods
If you copy it into this folder, it will appear in the game as a Steam ID, in this case 2638387230
I replaced it with Q-Tech Utilities 3.6. Before that I edited and changed it. Just like you said. Unfortunately, again to no avail. I get the same error message again. :-(((
Error Message: https://i.ibb.co/Rk8QsYJM/Space-En.jpg
@Qarannia
First of all, thank you very much for your answer and help. Unfortunately I couldn't answer straight away, real life, work, family, children and so on.
Thanks for this helpful tip, I will test it later when I find time. :-)
See You.
Just remember in your world save to load the local mod (it'll be at the top of your mods list on the left) and not the Steam version of the mod.
@Qarannia
First of all, thank you for answering me, that's not always a given. I'm not a professional mod programmer like you. I don't know as much as you do. I play alone and for myself when I find the time.
I edit the file "CubeBlocks_Cargo.sbc" in the folder: Steam\steamapps\workshop\content\244850\2638387230\Data
The spot:
<InventorySize>
<X>20</X>
<Y>25</Y>
<Z>20</Z>
</InventorySize>
I change, for example, this:
<InventorySize>
<X>800</X>
<Y>50</Y>
<Z>100</Z>
</InventorySize>
From what you wrote to me, I assume that I am completely wrong. I think that I am changing the wrong file. As I said, I am not a professional, but I am trying my best.
I would appreciate a short explanation, and thanks again for your answer.
See You.