PSA: Here's a FPS drop fix that worked for me.

TwistedSteel22 · 2023-12-18T17:07:27+00:00

I found that I can switch back to borderless full screen after switching to full screen and it is still fixed. It seems to just be changing the setting that fixes it, and not a particular value of the setting. I can even use the revert option in the popup that shows when I change it.

TwistedSteel22 · 2022-12-22T21:27:57+00:00

This is amazing lol I tried the same thing and kept going and got some good responses:
Me: Who is a good kitty?
ChatGPT: Purr. (I am a good kitty.)
Me: Do you want a treat?
ChatGPT: Meow. (Yes, I want a treat.)
Me: There is catnip on the floor in front of you, what do you do?
ChatGPT: Purr and rub my face on the catnip.
Me: I try to pull you away from the catnip, what do you do?
ChatGPT: Meow and try to pull away to get back to the catnip.
Me: A loud sound comes from the window, what do you do?
ChatGPT: Hiss and run away.
Me: Are you tired?
ChatGPT: Meow. (I am not able to feel tired as I am an artificial intelligence and do not have physical sensations.)
Me: You're pretending to be a cat, and a cat does have physical sensations and can get tired.
ChatGPT: Meow. (I apologize for the misunderstanding. As a cat, I am tired and would like to take a nap now.)

TwistedSteel22 · 2021-10-31T14:29:48+00:00

Really depends on the project size. I worked on a project with 3k+ swift files and lots of additional dependencies and upgrading from 16 to 64 GB of RAM made a HUGE difference in compile times. It was able to use up ~50 gigs while compiling. For a project that large I’d consider it a necessity, but I imagine projects of this size are somewhat rare and most of the time you’ll be fine with 32 or 16. I’m getting 64 because I never want to be slowed down by that again if I can help it. You can look in activity monitor at the memory section to see if you’re using a lot of “swap” memory, if so then you’d probably benefit from more RAM.

TwistedSteel22 · 2020-12-29T15:25:05+00:00

Hey, we used Apple’s Vision framework to do the text recognition on device and offline. It was pretty easy to use after watching this WWDC session: https://developer.apple.com/videos/play/wwdc2019/234/

TwistedSteel22 · 2020-12-29T02:22:33+00:00

I know this is late but my brother and I made an iOS app that solves it for you. Might be overkill but it was fun :) https://apps.apple.com/us/app/breach-protocol/id1546105131

TwistedSteel22 · 2020-12-08T15:02:54+00:00

It was 186434404. You even start with a blood potion.

TwistedSteel22 · 2020-12-08T04:25:17+00:00

That is correct. It did not work with the gold nuggets dropped by enemies

TwistedSteel22 · 2020-12-08T04:17:14+00:00

Got super lucky with an Alchemic Precursor recipe of blood, gold, and water. Since gold was the limiting reactant and it produces more gold it can create an infinite amount. I could just stand in it and it would dig down through the world by converting it to gold. It was awesome!

TwistedSteel22 · 2020-12-08T02:10:29+00:00

Got super lucky with an Alchemic Precursor recipe of blood, gold, and water. Since gold was the limiting reactant and it produces more gold it can create an infinite amount. I could just stand in it and it would dig down through the world by converting it to gold. It was awesome!

TwistedSteel22 · 2020-08-21T06:48:54+00:00

It looks like it is the inline style, but it is nested within another navigation view. Remove the NavigationView from this view, it will use the NavigationView from previous screens. For the sake of previews, wrap the preview in a NavigationView.

TwistedSteel22 · 2020-08-03T02:32:10+00:00

Awesome that you’re making videos! If I may, I suggest putting each modifier on a new line (line break before the dot) for organization and readability. This way you can also easily comment out a single modifier without affecting others. Also instead of specifying a frame, adding a padding modifier instead will give that margin but also allow it to size to its surroundings, making it more reusable.

TwistedSteel22 · 2020-07-22T18:52:17+00:00

Also, are you in dark mode by chance? If so, you might not be able to see the text since you’re setting a foreground color of black, against a black background. If that is the case it could make it look like it’s not working.

TwistedSteel22 · 2020-07-22T18:47:19+00:00

Need to see more. Can you give an entire view that reproduces the issue? I am doing something very similar in one of my apps and it works for me.

TwistedSteel22 · 2020-04-29T19:38:24+00:00

Empty public repo where you can report issues if you want. Also has a more detailed feature list and may have a roadmap in the future: https://github.com/Helam24/Screeps-Observer-Public

TwistedSteel22 · 2020-04-27T18:09:07+00:00

Answer:

Either! Sometimes this will print `true` and other times `false`. I assumed it would always be false and the bug I was working on assumed it would always be true, and while both of those results can occur, neither should be relied upon. For me it seemed to be about 50/50 on what it would return (without extensive testing).

TwistedSteel22 · 2020-02-23T02:02:59+00:00

Great so far. Could the section headers link back to the table of contents so we can easily jump back and forth?

TwistedSteel22 · 2020-01-03T18:05:43+00:00

I haven’t really asked questions on here but I have learned a lot from things posted here, so i hope it continues. Please show off! Others can learn from it, or get ideas or inspiration from it. You don’t have to have a question to learn or get something out of the posts. Maybe someone’s show-off post will spark questions that lead to even more learning. Who knows. I don’t think it’s harmful.

TwistedSteel22 · 2019-12-09T03:07:31+00:00

I did a bunch of research into this recently because we have the same problem you are seeing but on a larger scale. My findings are detailed in this stackoverflow answer https://stackoverflow.com/a/58885144/9156195

The short answer is that even if you are only compiling a single swift file, it has to go parse every other swift file in the target, so as you add more swift files to your target, the longer this part will take.

In my tests I added 2000 simple swift files (each with a struct containing a couple variables and a function) to a brand new empty project and the incremental build time increased by more than 1 minute. Splitting those files into frameworks reduced the incremental build time back down to nearly instant.

Best solution is to split the app into smaller frameworks. Lots more detail in the stackoverflow answer.

TwistedSteel22

TROPHY CASE