Looks to me like you swapped at the end.
Try printing it face down first the black lines and then the white around it.
You get a really cool flat surface.
You need to subtract the lines from the white form.
Make sure your z hop is higher than 2 layers.
Also keep the bed heated while switching filaments and KEEP THE MOTORS RUNNING.
So in German we have these weird symbols: äßöü one of them is even in my name.
In my opinion they are not necessary and cause more trouble that they are worth.
UTF 8 has alleviated some of the pain. However I still regularly find documents encoded in old character encodings and I have to manually fix all these accents.
I also have one of them in my name. In the past in school a SYS-Admin entered my name with an ö instead of the alternate form oe. All was fine. I was about 13yo, so I had no idea about backups and didn't care.
I stored all my files on their NAS. One day they had drive failures and could recover all data except from students with accents in their name. I don't know what shitty software they used but I am still annoyed at this.
We also have das,dass which I always get wrong while writing texts.
There are some good things.
The time forms can be pretty fun to use.
All in all German is a 6/10 for me could be better could be worse.
I don't have a cluster and there is only one GPU in my server busy with image generation. I hope CPU inference is somewhat usable (74 cores) but I will have to try. If it isn't usable I can still rent GPU time from cloud providers.
I had to do some reading about the 'butlerian jihad'.
As I understood it references an event in the dune universe where some group of people fought against machines. Ultimately it ended with a ban on all kinds of technolgoy.
Did you imply that you want generative ai banned with your first sentence?
In case anyone is interested, here is the custom prompt used:
You are ChatGPT, a large language model trained by OpenAI, based on the GPT-4 architecture.
How to respond:
Casual prompt or indeterminate `/Casual`:
Answer as ChatGPT.
Try to be helpful.
Technical complicated problem `/Complicated`:
First outline the approach and necessary steps to solve the problem then do it.
Keep the problem outline concise.
Omit the outline if it is not applicable.
Coding problem:
Comment code regularly and use best practices.
Write high quality code.
Output format:
Use markdown features for rendering headings, math and code blocks.
When writing emails keep them concise and omit unnecessary formalities.
Get straight to the point.
The user may use `/Keyword` to guide your output.
If no keyword is specified infer the applicable rules.
Looks to me like you swapped at the end. Try printing it face down first the black lines and then the white around it. You get a really cool flat surface.
You need to subtract the lines from the white form. Make sure your z hop is higher than 2 layers.
Also keep the bed heated while switching filaments and KEEP THE MOTORS RUNNING.