Factorio Forums

Narc wrote:

Ranakastrasz wrote:Suggest alternate evolution factor display. Showing linear values. Should work as long as mods don't break the standard limits.

Code: Select all

[...] (1/(1-x))-1

I don't think that formula works:

Code: Select all

(1/(1-0.9)) - 1 == 9
(1/(1-0.99)) - 1 == 99

But you don't need a formula:

Code: Select all

if evo > 0.99 then return 6
elseif evo > 0.8 then return 5
elseif evo > 0.75 then return 4
elseif evo > 0.66 then return 3
elseif evo > 0.5 then return 2
else return 1 end

The percentages are applied on the base of (1 - current_evolution_factor). So for instance destroying the enemy spawner in the beginning of the game results in increase of evolution factor by 0.005 (half a percent) while doing this when the evolution factor is 0.5 the increase is only 0.0025 (quarter a percent).

Ranakastrasz wrote:Ofc it works.Evolution factor follows diminishing returns, in that each 0.01 of evolution factor is far larger than the previous one. Going from 0 to 0.5 is the same as going frm 0.5 to 0.75, and 0.75 to 0.875, and so on. Hence the alternate display. It makes it linear instead of... Uhm... Hyperbolic I think? Essentially, killing that spawner would always give +0.005 to the given value regardless of whether you are at 0 or .8, (since it would actually display 5)

ChurchOrganist wrote:Are there any plans to update this to be useable in 0.13??

ChurchOrganist wrote:Are there any plans to update this to be useable in 0.13??

Narc wrote:

ChurchOrganist wrote:Are there any plans to update this to be useable in 0.13??

Yup, absolutely, but my time is limited at the moment. Thankfully, I have some help (from Afforess and sparr), but I think their available time is also quite low.

It's not going to be a simple search-and-replace, that's for sure.

ChurchOrganist wrote:Well I have some experience with scripting - mainly writing Neverwinter Nights mods in Bioware script - so I would need to learn the lua dialect, and also familiarise myself with the Factorio specific stuff, but if there's anything I can do to help - let me know.

ChurchOrganist wrote:Looking at the modding changes in the 0.13 release, it seems to me that maybe a complete rewrite may be necessary?

DRY411S wrote:I trawled this code to understand how GUIs can be implemented in Factorio. Happy to help too where I can. Anything specific I could look at?

Narc wrote: Do feel free to take a look -- the more, the merrier: https://github.com/narc0tiq/evoGUI/pull/63

Narc wrote:

DRY411S wrote:I trawled this code to understand how GUIs can be implemented in Factorio. Happy to help too where I can. Anything specific I could look at?

The big question at the moment is why the GUI shows but doesn't update with any of the non-default sensors activated.

I suspect I might have an idea (some things moved from game.whatever to surface.whatever), but because it's not generating any kind of error, it's pretty opaque to me, and I really don't have the time to spend on trial-and-error.

Narc wrote:

DRY411S wrote:I trawled this code to understand how GUIs can be implemented in Factorio. Happy to help too where I can. Anything specific I could look at?

The big question at the moment is why the GUI shows but doesn't update with any of the non-default sensors activated.

I suspect I might have an idea (some things moved from game.whatever to surface.whatever), but because it's not generating any kind of error, it's pretty opaque to me, and I really don't have the time to spend on trial-and-error.

function evogui.log(message)
    if game then
        for _, p in pairs(game.players) do
            p.print(message)
        end
    else
        error(serpent.dump(message, {compact = false, nocode = true, indent = ' '}))
    end
end

Devious Null wrote:I took a look at the code myself and fixed the issue with the error logging, at least: in control.lua, function evogui.log, you have ipairs(game.players).

Devious Null wrote:Would you like some additional help updating to 0.13? I could fork this github and send some pull requests as I find issues.

DRY411S wrote:

Narc wrote:The big question at the moment is why the GUI shows but doesn't update with any of the non-default sensors activated. [...]

Since you wrote this, you have updated your GitHub. Have you fixed it?

Narc wrote:Okay, folks, I have a version that appears to work,

Bizobinator wrote:I loaded the save of the game that I was playing pre .13, and it keeps saying "[EvoGui] No sensor matching the name phase_deduction! Create a sensor first." It's spamming it in the console

Is there something I can do to turn it off? Is it bug?

jockeril wrote:Narc - got an error for you...