i'm also having an issue where a lot of the time i cant mix coal and iron to get steel, it works some times but a lot of the time it only wants to make a coal ingot and then the ingot of coal looks like it'll be made but it never is
Coal ingot and Zinc Ingot do not exist, thus of course it'd never be made, though, It's really not supposed to show coal ingots at all.
As for steel alloy - if there's ever an issue with it not displaying, try removing the ore and putting it back in, and/or moving the smelter, as the detector might have gotten blocked by something (unlikely)
If those don't work, go for a save reload rather than trying anything else, but first, remove the ore that you can, then do the reload.
All ore is *supposed* to get "frozen" in the furnace when you try to input it for smelting - The "actor" is supposed to get locked
Currently only "one" actor is getting locked, resulting in some misc bugs/exploits with the other ore and smelting - but the one that is locked, is not a bug.
The "not enough fuel" is an entirely different issue altogether.
Not enough fuel can be caused by various thing
1) other stations/physics hit boxes could be in the way of one or more of the detectors - From my observation I ASSUME... there is a "Fuel detector" an "ignition detector" and an "output detector".
The Fuel detector is tied to the meter that visibly displays how much fuel is present - you can exceed this, though the meter will just remain in red for the majority of that. - The "ignition" detector IMO is what causes the majority of "Not enough fuel" as this would be the detector that targets a piece of coal or wood and starts burning it for heating and smelting. - If this detector fails in some way, it won't burn wood, won't tell there's wood to burn, and thus, nothing will occur. - Output Detector will allow heat to work, but prevent smelting to work, if only the output detector is blocked (near the casting tray) - when only this happens, its usually simple enough to fix.
2) a second possible way is both fake fuel and fake readout - Not much I can really say about this one, sometimes it just seems like fuel disappears or that the readout is empty with fuel in it. - saving and reloading will usually eliminate this - as its usually either the fuel is actually burnt already, and for whatever reason their visuals remained, or perhaps the fuel detector had something happen, I don't know.
3) This way is more user error, and can be avoided by not trying to smelt more than a small small number at a time - and that's by putting too much ore in, and requesting too much output - not only would it take forever to heat up for each additional ore chosen, but the thing only reads so much fuel at a time, right? - even if it can have more plaed inside that it knows what to do with.
Saving and reloading will purge the non-save file data, yeah - which includes customers
The reason the additional customers are spawning IS NOT LIMITED TO WHAT I'M ABOUT TO SAY.... but what I say below here is DEFINITELY one of the main ways.
Shield Customers currently cause an issue when they "Wait" for the second item, No matter what, if you sell anything to a shield customer, they will cause one more additional customer to spawn, one for every time you repeat this. - These are not intentional spawns, and as a result, other issues associated with them are not necessarily bugs, because the additional customer itself is the bug.
Avoidance can be done by simply dismissing Shield customers right off the bat, and if you accidentally allow two or more customers, it is likely safer to just go ahead and save and reload then and there, rather than wait.
additional as I said, not limited to Shield - There could be some other less obvious things that are triggering additional spawns as well - and while I've never seen it personally, The custom difficulty also has a setting for "Multi-order" which sounds like a customer could ask for two or more items, not necessarily being shield(s) - if this DID occur ever, that customerr too would likely cause another customer, as well. - since it seems tied to the "Waiting"
I'm having an issue where the paper signs are blurry and unreadable. The blueprint paper is the same way, so I can't figure out how to do anything
This is what it looks like
I'm running on the latest version of the game which is 0.1.0
My pc specs:
Nvidia GTX 970
AMD Ryzen 3 1200 Quad-Core
8 GB RAM
And it isnt my graphics settings because every other texture in the game is clear
Ensure first that if you downloaded 64bit before, that you redownload 64bit as it was accidentally a reupload of 32bit originally
However, now beyond this.
Go to the the blueprint or to the podium in your room, keep the contents of either to one side of the screen, and pause the game
go to graphics settings, and with either effects or shadows, keep futzing with them until the clarity changes - You can keep doing this until your setting is what you want it at, and keeps clarity.
Why specifically it decided to start breaking/failing to trigger, I don't know, but it has something to do with those two settings primarily, and with the settings failing to update or trigger or something. (possibly as a whole)
If you keep adjusting those one of those two, though, eventually it'll correctly update
For the most part, if you could please re... eeehh... I guess theere has been video postings.. it doesn't really matter... but feel free to redact some of the info here, I won't stop you if you decide to, and would encourage it.
anyway onto the matter at hand.
Yes. Some places unload (partially?) when the player is not within their cell/region - This causes foreign entities (anything that isn't ore is foreign, this includes the player(save/reload)) to fall through the now unloaded surface, and generally, into the void, however its not always directly into the void, (player mostly), but it is always "gone"
The area unloading is not specifically "a bug" as that is the intended purpose.
Lost crystals can (somewhat) be solved with Slipcor's save fixer
the most recent one (for 0.0.9e) can be used for some features in 0.1.0o - there is MINOR support for difficulty and primary save file - if you have 3 normal files (I think) and this one in particular is your "2" (3rd, I think) then the save fixer will have a lot of trouble being of any help, as it will be next to impossible for it to identify the save file - it isn't yet designed to support multiple saves.
but if its the primary file (of a difficulty, I believe, so if you have 1 hard, 1 normal, and 1 easy, you can fix any of them.. I think.... I'm not sure, as I haven't had the need to, and it hasn't been priority in my mind to check it cause it isn't updated)
There's no way to recover the crate, though that's small potatoes cause you can chop essentially infinite logs for essentially infinite crates.
If you can't recover the crystals, there's a few options still that remain.
one is to wait till you can
another is to just forget about it for the time being, as the [redacted(long)] this version
And the last, very last, would be to restart your save...
technically there's one before that too
you can try to be like Slipcor and break open your save and edit the crystals entries yourself - If they don't exist, the engine is programed to make them exist (when you use them, correctly, the engine will reload them on the next save and reload, )
as Slipcor does, you should backup your save if you try this, just like his fixer, as 1 wrong step can instantly bork the save file.
Not a "bug" per se
0.1.0o has a new station system as well as smelter system, among other things like save slots and difficulty.
Your 0.0.9e doesn't have equivalent difficulty identification - would default as a primary(non numbered) save slot - If it had the smelter, it's possible that could update smoothly however
There building system aforementioned includes the stations being saved to the save file, so it can track their updated positions on the map and such.
now that they're scripted to save in the save file, they're also scripted to reload from the same file - meaning if their entry in the save file doesn't exist
They don't exist.
And 0.0.9e - didn't save them to the save file, it spawned them in with the engine, unloaded them, and reloaded them, all engine.
So a 0.0.9e (or earlier) save file doesn't have entries to reload them.
0.1.0o on a new save trigger - spawns the stations in for the very first time and that alone. - which gives them an initial entry to reload from
_______
Long story short. - Due to drastic feature changes and inclusions, it is impossible to use that save
While it was possible in many cases to ignore changes and continue a save before, these are fairly game-breaking
Alpha version 0.1.0: I gave a man the wrong sword, because I read his request wrong, and it then started to rain normal guards into my shop. I haven't been able to recreate it, but man do I have some cleaning up to do...
