Release EDSY - The ship outfitting tool formerly known as E:D Shipyard; reimagined, redesigned, reborn

.................
  • In the checklist under details it states Overcharged G5 x 1, despite I entered a 6 in the box. And in G1-4 it states x 5, but I also entered a 6 there...

Regarding the Overcharged G5 x 1 issue: this seems to occur when you change your module values manually on the outfitting page (instead of choosing 100%, 80%....). I think a way to solve this could be to just use the settings on the analysis page for module grades and number of rolls.
 
A bit confused by the "Analysis" Tab. I want to figure out what materials I need to create a specific, engineered build.

When I put a six into every field in "Rolls to complete each grade", it calculates that I need five materials for each grade. For G5 its always only one material, despite what I put in the field. In this case it should be for example 6 Zirconium, as I put grade 5 100%, 6 rolls and you need 1 Zirconium per Grade 5 roll.

Questions:
  • How does the calculation work exactly? Am I missing something or is there a bug.
  • In the checklist under details it states Overcharged G5 x 1, despite I entered a 6 in the box. And in G1-4 it states x 5, but I also entered a 6 there...

That's because in the build you've linked, the target modification on the weapon is flagged as a "legacy" blueprint, rather than having a progress percentage like modern modifications. If you click the 100% button on that module and then re-run the analysis, it then prescribes the expected six G5 rolls with corresponding material costs.

The G1-4 rolls will still be predicted to take only 5 rolls each, which is because you don't have to actually get to 100% at each grade to progress, so it estimates that if you would need 6 rolls to get 100% (which isn't true, of course, but going with your inputs) then it would only take 5 rolls to get close enough to move on to the next grade level.
 
Thanks a lot for the explanation, that makes it clear. Sure, I just chose some example inputs to make my point clear.

For me a bit less automatic calculations would work as well (perhaps a togel)
 
Updated to v3.7.4.1:
  • added detection and warning of likely MSIE URL length limit issue
  • fixed nonstandard internal slot names for some ships when exporting to Journal/SLEF format
  • updated 1D Meta Alloy Hull Reinforcement mass
 
Same for me, more specifically, it seems as if clicking on some items (let's use Shield Generators, definitely happens on these) will scroll the page down below where anything visible is, hence you get a screen of grey. Also, using the scroll wheel will allow you to scroll the whole page down below the visible portion, assuming that's def not intended.

I'm on Edge (Chromium).

BTW, a workaround is to drag and drop the modules into their slots, annoying but it works.
 
Same here.
When double-clicking a weapon module to add it to the ship, the page will scroll down to the bottom, where there is a large empty area, which shouldn't be there in the first place.
For me, this behavior happens in Brave, but not in Chrome.
Since the browser seems to vary across users, it may have something to do with which browsers contains your stored blueprints, but this requires confirmation.
 
Just wanted to let folks know that I've spent some time investigating this scrolling issue in Chrome (and related browsers) but so far I'm stumped. I'm tempted to say it's a bug in the browser since it looks like documentElement is being expanded to contain the scrollHeight of the modules, which it shouldn't do since the modules are already inside their own scrolling container which ought to have a height fixed to the viewport via flex boxes. But I haven't been able to recreate the issue in a minimal mockup with the same layout, so I still don't know what exactly is causing it on EDSY.

If anyone has any webdev/CSS expertise and wants to take a look, I'm certainly open to ideas!
 
If anyone has any webdev/CSS expertise and wants to take a look, I'm certainly open to ideas!

Took a quick look and adding position: relative to
#outfitting_modules_group_hardpoint
#outfitting_modules_group_utility
#outfitting_modules_group_component
#outfitting_modules_group_internal


Seems to fix it, possibly even without breaking anything else. I didn't test it too thoroughly.

This is probably some issue with css containers-within-containers sometimes, maddeningly, not working as expected if the parent/child containers don't have the exact right positioning style set. I mostly try to do backend programming and only vaguely understand this so I don't really have a good explanation for the "why" here (or even if this is the correct way to fix it).
 
Took a quick look and adding position: relative to
#outfitting_modules_group_hardpoint
#outfitting_modules_group_utility
#outfitting_modules_group_component
#outfitting_modules_group_internal


Seems to fix it, possibly even without breaking anything else. I didn't test it too thoroughly.

This is probably some issue with css containers-within-containers sometimes, maddeningly, not working as expected if the parent/child containers don't have the exact right positioning style set. I mostly try to do backend programming and only vaguely understand this so I don't really have a good explanation for the "why" here (or even if this is the correct way to fix it).

Thanks for the tip! Changing the position on that container from static to relative did the trick. I don't understand why either, but it works for me at least.

Updated to 3.7.5.4 with this fix and a correction to the Pacifier's falloff range.
 
Quick question: when will importing data from coriolis.io work?

It when I click the "Restore Data" button", is says it will work with JSON data from Coriolis; but as soon as I paste the datae is says there was an error and Coriolis data import isn't supported yet.
 
EDSY specifically supports SLEF format, which is a community-defined JSON format based on the Journal Loadout event format. EDSY can import and export in this format, as can Inara, but Coriolis does not support it yet; you'd have to ask them when they plan to implement it.

edit to clarify: once upon a time I reverse engineered Coriolis' own JSON export format and built up all the mapping tables to convert them to EDSY's internal representations, which allowed for import from Coriolis. But of course they made changes to their format after that and it wasn't feasible to keep trying to maintain that support, so I dropped it. But the code to detect the Coriolis format is still in there, hence the message that it isn't supported.
 
Last edited:
EDSY specifically supports SLEF format, which is a community-defined JSON format based on the Journal Loadout event format. EDSY can import and export in this format, as can Inara, but Coriolis does not support it yet; you'd have to ask them when they plan to implement it.

edit to clarify: once upon a time I reverse engineered Coriolis' own JSON export format and built up all the mapping tables to convert them to EDSY's internal representations, which allowed for import from Coriolis. But of course they made changes to their format after that and it wasn't feasible to keep trying to maintain that support, so I dropped it. But the code to detect the Coriolis format is still in there, hence the message that it isn't supported.


That's completely understandable. But, may want to remove the part of the code where it says it supports importing Coriolis then. To help others out.

I currently use both sites myself. I like the look/layout a little more of Coriolis.io, but EDSY has several more components that the other site doesn't.

But, great work on the site. I certainly enjoy using it and glad it's around.
 
Hi,
Is there a trick to using the delete button that I'm missing? I have a few builds stored that I'd like to remove, but whenever I've tried the delete button it never seems to work.

Edit: never mind, I'd been using the delete button in the outfitting screen (which doesn't seem to work), but I've just found the list of stored builds in the shipyard screen instead (where the delete button does work). :)
 
Last edited:
Top Bottom