I’m not sure why bbl can not get someone who can write technical documentation to rewrite the English version of Bambu studio. I guess it is a similar problem with other languages. and it’s also a problem with Orca slicer, too (but I can’t blame bbl for that). I never noticed this when I used Cura, but maybe I didn’t notice it, since I was more used to it. Perhaps I should raise a ticket when I notice an error, but in reality, the whole thing needs sorting out, and some underlying specification/layout defined.
That’s a pretty vague rant, so it is not clear what you are asking Bambu to change.
I’ve submitted a couple of corrections to Studio spelling and phrasing via Github. They were incorporated in the next release.
OrcaSlicer builds on the Studio code, so at least one of those changes is now also reflected in Orca.
Or you could ask for your money back.
I feel your pain but truth be told, this is open source software written by committee. It shows in so many ways the most obvious points are the two separate menus.
Here
And here
There is a basic format called the “Windows Style” guide that has been around since 1988. You will recognize that format here:
The Windows style guide is where programmers have been encouraged to follow the style of File, Edit, View and Help as basic principles of menu construction along with their ‘ALT-’ hotkey functions.
Link to the current apps style guide
Why do open-source developers ignore this industry standard? I have two theories behind this, which come from my experience first working as a programmer since the '80s(that was before they self-anointed themselves with more flowery term ‘developer’) and second, working alongside developers over the years in a program management role.
The first theory is that some academics display a kind of ‘nose-up-in-the-air’ arrogance, always trying to prove that they are the smartest people in the room by reinventing the wheel. If Microsoft invented it, they’ll take an entirely opposite approach.
The second theory involves the students of these academics, who are conditioned at universities to believe that if they’re not constantly innovating, they’re falling behind. As a result, adopting proven technologies is often dismissed in favor of something ‘new’ under the guise of innovation or progress. I’ve told many developers over the past 40 years, ‘Change ≠ Progress.’ Wisdom comes in knowing the difference, which can only be gained through years of experience, not from a classroom or a book. Deadlines have a way of forging people into either useful contributors or showing them the door. This is particularly significant in the aerospace industry, where failure is not an option, as Boeing continues to learn the hard way.
One of the most challenging aspects of working with software developers is keeping them focused and on task. There’s an old joke among program managers: ask a software developer if it’s done yet, and the answer will be, ‘No, but when it is, you’re gonna love it.’
So given that backdrop, is it no wonder that readability or even spell-check is always going to be back-burner?
None of this relates to the OP question.
Having been in software development for 35 years and 28 years owning my own software development company I have a few thoughts to add.
I owned the MS UI guide in book form decades back. I used it as a bible.
I started writing software for several earlier operating systems, Windows was my primary business for a couple of decades.
I moved through desktop applications to adding web front-end and back-end solutions through to mobile development for iOS and Android (and several more previously including MS mobile).
I have been a dual Windows and Mac user for well over 15 years out of necessity.
Microsoft dropped its use of the traditional menu UI method from most of its software to replace it with the much-maligned ribbon bar.
Trends change, for good or bad.
The need to create cross-platform solutions often brings unfortunate compromises. I always created native UIs myself.
The question that should be asked about the UI is; can you work out how to do everything? I can. My abundance of experience with UIs is greater than most though.
It wasn’t the gui, so much, but some of the lack of logic in the questions/commands. Too many to quote, but I’ll see if I can find an example, Sod’s law excepted. OK, here’s one.
They ask if you want to ‘keep changed settings’ that suggests a ‘yes’ or ‘no’ answer but the choices you get are ‘Transfer’, ‘Discard’, ‘Save’.
The settings are labelled ‘Old value’, ‘New value’. Is the ‘Old value’* before you made the changes, or are they the changes that will be overwritten by the new values? Which way is ‘transfer’ going? It’s just sloppy language, pretending to be technical. It is far from concise. and then ‘Remember my choice’ - will you ever see that screen again, what is remembered? If it’s the highlighted button how does that help. *should it be ‘Old value’ or ‘Old values’?
Then, if you want a bit of gui gripe - why print in light grey on top of a lighter grey? Some software developers need a brain transplant, in particular so called web design. Here’s an example. Some years ago, about 1997, IBM produced Java for VisualAge. The gave away packs of coffee beans. Others jumped on the band wagon, everything Java (like now you have to have an ‘i’ or an ‘e’ in a car name). Easynet thought it was a good idea, and their manual for their modems was printed with pictures of heaps of coffee beans, cups of coffee, and the like, in dark brown. The dimwits printed the text over the top in black.
As you get older, you get more right wing and whingey, and so you should. You gotta keep these whipper-snappers in order.
and, being pedantic, it’s ‘Max.’
A quick one on Orca slicer, nowhere could I find in the tutorial, when testing for pressure advance, if ticking the box made any difference.
That’s a great example. Your suggested solution is also on-point. I would add that this is also a side-affect of when one does not use native speakers to translate or write copy text.
Well… someone has to… right???
I’ve not got an ams, but it seems very confused to many folk. Fwiw, I was poking around in the directories that Orca uses, to see if there was something easy and obvious that could be changed to remove grid infill - no harm in hoping. I found a json file with a list of forbidden filaments. I guess that could be altered to allow some tpu in the ams. Although Orca is a fork of Studio, iirc, I don’t think it changes studio at the core, just puts a wrapper around it. As I’m only using a 0.6 mm hs (cht type) nozzle and a p1s, I could probably strip out a lot of stuff, the only choice I would need is the filament.
On Github, a user requested a better description.
Studio Public Beta 1.9.0:
Requests on Github are more likely to be acted upon. The forum is just for complaining to other users, don’t expect Bambu to pay any attention.
I don’t think you can remove Grid infill without editing the source code and re-compiling. You could edit the .json files for the System presets to change the defaults, but those files are overwritten with every update. Better to just modify the system preset and save with a new name as a User preset and use that as your default.
Thanks, Ikraus. I realise bbl will only act on stuff that effects their bottom line. At the moment, I think other longer established manufacturers have products that are lower cost, and superior, in many instances and open source, so bbl needs to be careful. There is a world of difference between being a computer eco system, where it is electronics and restricted software and customers, all a controllable environment, compared to 3d printing, which adds in filament, uncontrolled software (designs), and a more ‘difficult’ customer base, and even the weather, which is more like herding cats.
I will try to find the system presets, and change the default infill, if possible.
For a Windows system,
Help>Show>Configuration Folder will take you to the hidden folder C:\Users\%username%\AppData\Roaming\BambuStudio
from which you can reach the file C:\Users\%username%\AppData\Roaming\BambuStudio\system\BBL\process\fdm_process_common.json
which can be edited to change "sparse_infill_pattern": "grid",
to the pattern of your choice.
These settings are then inherited by all the other presets I’ve looked at.
Again, any preset inheriting these settings will be changed back to Grid with every Studio update. Changes made to a User preset will be retained.
While you were writing that, I found the following.
I’m not quite sure, but for my p1s, it seems that ‘OrcaSlicer-resources-printers’ has a file ‘c12.json’ and also the file ‘fllament-blacklist.json’, which may have some useful settings. ‘resources-profiles-bbl-process’ is where the infill patterns can be set, but they seem to inherit from some basic settings- I added '“sparse_infill_pattern”: “gyroid”, ’ Also ‘AppData-Roaming-OrcaSlicer-user- mynumber-process’ has what looks like your last saved settings. in ‘something -Copy.json’.
I hadn’t found the common.json. I use ‘Everything’ for finding stuff. Hopefully now grid will not appear as the preferred infill. There must be a list of infills, That could be removed. Thanks for your help.