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
A lot of ppl were annyoed at the change, but it is deliberate, to force the player to build logistics to get the ore to the surface, and not just smelt at the ore extractor, which is too easy.
On plentiful settings, the blast furnace uses 32 ore/bar, at least for T4 ores. A smelter with the Arc addon uses 16 ore/bar for T4 ores, while normal smelters use 4 ore/bar for T1/T2 ores.
ugh
They work without induction, oddly. Slower with it. Maybe a bug
Both the OreSmelter and the ForcedInduction classes have a mbTooDeep variable, and they are independent of each other. The variable in the OreSmelter class is set in the instantiation function, and is apparently only used by Arthur/missions to alert the player that the smelter is starved. The OreSmelter variable does not appear to be changed by the forced induction class, so the smelter will always be reported as "too deep" below -40.
Also in the OreSmelter instantiation function is set the mrSmeltTime variable, and it's set to 1024 if the smelter is below -40. The forced induction class sets the mrBurnRate variable in the OreSmelter class. During smelting the smelter decrements the burn rate from another smelt time variable (mrRemainingSmeltTime) during the course of the smelting cycle. Therefore, if the smelter is below -40, the smelt time will always be "really long" no matter what induction level is on top.
Seems like it shouldn't be hard to fix: add a method to OreSmelter to change the mrSmeltTime and mbTooDeep variables so that the forced induction can correctly set these two variables. But, what do I know - I'm an engineer, not a programmer! :)
if the Handbook wasn't hardcoded then so much would be easier