I'm loving the humour of showing the bad things that can happen. I don't really need the tutorial myself which is well made and informative but I'm loving these videos anyway :)
I love the way you did and narrated this tutorial. It's so chill yet to the point without extraneous blathering and filler, I feel like I'm watching David Attenborough explain Stationeers xD
@@KittenyKat You make my day :D Thanks for the appreciation, and I aim to improve on the quality in the future because a few days ago I have now finally started to EDIT my vids, so stay tuned :)
Great little teaser for learning to IC code at 4:55 , God! You got me to make the leap into coding, so maybe this will encourage others to do so, as well :)
This was a great explanation! Even though I'm an old Stationeers player, I've learned a lot from your videos! Thanks for the content. Keep posting Stationeers videos!
Thanks. I keep hearing that those vids are helpful, but I must also keep reminding myself that they aren't exactly pushing the boundaries - and my stations look like ass. I've just visited another player's station, and they have put soooooooooooo much work (and intelligence) into their infrastructure, I can only dream of being that organized and aspiring. Oh well ... maybe in the future.
Wow, I don't remember that wall vent option on the passive vent. When the heck was that added? 😅 Looks useful, though a "digital valve" version of it would be even more useful so you could seal it if a leak was detected!
Hello, first I'd like to say your video on IC10 Programming really helped me get started, loved the video. However I tried writing a script a automatically control my atmosphere and its mostly functioning but there are a couple things just not working and I can't figure it out. I came to this video to see if I could find what I needed but unfortunately I did not. Is there any chance I could send over the script for you to look at?
Not sure. I have a decent rig, so things are smooth most of the time. I am a very active reader of the Stationeers Steam forum and Discord server, and I can't remember ever having heard talk about missing optimizations in 2024. I also keep seeing people who run this game on a potato and even make (not too high framerate) videos. So, I'd say the game is optimized enough to call it "optimized".
@@OwnerOfTheCosmos I really like such games. But due to my weak laptop, I am trying to make sure that I can play some games in the suggested system, it seems to be usable, but I am having trouble optimizing it. Thank you for the complete answer
I heard the main bottleneck with Stationeers may be too few hardware threads (which is amount of processor cores or amount of processor cores times two depending on hardware) and too little system memory. Store recommends 8 threads and 8 GB but I would rather recommend 16 GB.
Following such rules is for beginners, so that they find an effective way without having to invest a lot of time to reinvent the wheel, and so that they don't get lost in a jungle of their own making. I've been doing this for 4 decades. The project is finished, effective, readable, and future development doesn't need to be considered. sgt writes 0 or 1 into the target register (mentioned first), depending on whether the pair of values (mentioned last) has a "a > b" relationship. sgtz is a short version of that where "b" doesn't exist, because the statement "..z" implies it to be zero, so "a > z". "lbns" is "load batch named slot". The series linked in the description is a programming tutorial that explains these: ua-cam.com/video/UklimGea_Og/v-deo.html
@@OwnerOfTheCosmos since I am a total beginner in coding, what has helped me tremendously is to take the extra time to give all my registers names. When using an AND or OR command - it makes the rules I set up much more readable. I know that writing everything into r0 is more effective and time efficient, but using naming conventions has helped me personally in the beginning.
This is assembly programming, quite low level stuff. Assembly programming languages usually have shortened mnemonics like these instead of proper instruction names.
I'm loving the humour of showing the bad things that can happen. I don't really need the tutorial myself which is well made and informative but I'm loving these videos anyway :)
Thanks, that's very kind of you, always appreciated!
I love the way you did and narrated this tutorial. It's so chill yet to the point without extraneous blathering and filler, I feel like I'm watching David Attenborough explain Stationeers xD
@@KittenyKat You make my day :D Thanks for the appreciation, and I aim to improve on the quality in the future because a few days ago I have now finally started to EDIT my vids, so stay tuned :)
I second this. I have some experience with stationeers already, but I keep on watching because they're just too good.
:D ♡
KABOOM!!!!!!!! You did it to me again. I was half expecting it this time mind. I am such a wimp.
💣
Great little teaser for learning to IC code at 4:55 , God! You got me to make the leap into coding, so maybe this will encourage others to do so, as well :)
This was a great explanation! Even though I'm an old Stationeers player, I've learned a lot from your videos! Thanks for the content. Keep posting Stationeers videos!
Thanks. I keep hearing that those vids are helpful, but I must also keep reminding myself that they aren't exactly pushing the boundaries - and my stations look like ass. I've just visited another player's station, and they have put soooooooooooo much work (and intelligence) into their infrastructure, I can only dream of being that organized and aspiring. Oh well ... maybe in the future.
I never knew about the wall vent. Now it makes sense. Thank you.
Every time the computer goes to run a bit of code that I've made I Will Always Forever picture that sound 4:47
@@bombsquad1989 Wlblblb
Gr8 vid. Thx, as always
Wow, I don't remember that wall vent option on the passive vent. When the heck was that added? 😅 Looks useful, though a "digital valve" version of it would be even more useful so you could seal it if a leak was detected!
That's a very good idea, and I just wrote it in the (pretty flooded) suggestions channel on Discord (with attribution).
Hello, first I'd like to say your video on IC10 Programming really helped me get started, loved the video. However I tried writing a script a automatically control my atmosphere and its mostly functioning but there are a couple things just not working and I can't figure it out. I came to this video to see if I could find what I needed but unfortunately I did not. Is there any chance I could send over the script for you to look at?
Sure! You could find me on Discord (@owneroftheplace), or you could drop a link here to a pastebin.
How well is that creative tool working for ya?
Since this is singleplayer, it works fine.
Is the wall vent new? I got 3 episodes into this and learned something new. 1050 hours into the game now, still learning…
:)
I don't know how new it is, I didn't witness it coming in. Must have been last year or earlier.
Is this version optimized? Or it has a fps problem like planet crafter
Not sure. I have a decent rig, so things are smooth most of the time. I am a very active reader of the Stationeers Steam forum and Discord server, and I can't remember ever having heard talk about missing optimizations in 2024. I also keep seeing people who run this game on a potato and even make (not too high framerate) videos. So, I'd say the game is optimized enough to call it "optimized".
@@OwnerOfTheCosmos I really like such games. But due to my weak laptop, I am trying to make sure that I can play some games in the suggested system, it seems to be usable, but I am having trouble optimizing it. Thank you for the complete answer
I heard the main bottleneck with Stationeers may be too few hardware threads (which is amount of processor cores or amount of processor cores times two depending on hardware) and too little system memory. Store recommends 8 threads and 8 GB but I would rather recommend 16 GB.
@@OwnerOfTheCosmos thank you
That programming is anti-pattern.
What is sgtz what is lbns.
Following such rules is for beginners, so that they find an effective way without having to invest a lot of time to reinvent the wheel, and so that they don't get lost in a jungle of their own making. I've been doing this for 4 decades. The project is finished, effective, readable, and future development doesn't need to be considered.
sgt writes 0 or 1 into the target register (mentioned first), depending on whether the pair of values (mentioned last) has a "a > b" relationship. sgtz is a short version of that where "b" doesn't exist, because the statement "..z" implies it to be zero, so "a > z".
"lbns" is "load batch named slot". The series linked in the description is a programming tutorial that explains these: ua-cam.com/video/UklimGea_Og/v-deo.html
@@OwnerOfTheCosmos since I am a total beginner in coding, what has helped me tremendously is to take the extra time to give all my registers names. When using an AND or OR command - it makes the rules I set up much more readable. I know that writing everything into r0 is more effective and time efficient, but using naming conventions has helped me personally in the beginning.
This is assembly programming, quite low level stuff. Assembly programming languages usually have shortened mnemonics like these instead of proper instruction names.