The Lounge 2018: So... How Are You Doing? Edition.: Page 3

The Lounge 2018: So... How Are You Doing? Edition.

Megalomaniak

@TwistedTwigleg said:

@Megalomaniak said: ‘ways i’ve started fiddling with a new theme for the forum based off of godotengine.org

Looks great! I’m kinda sad to see the old theme go (I like the dark colors as they are easier on the eyes at night :smile: ) but the new theme looks like a great replacement! The consistent look should also help people coming from godotengine.org and the QA.

I can definitely look into adding custom stylesheet choice for a dark theme once I'm done with the new default.

emo10001

Last book I read was Ready Player One, which I loved....but it sure made the movie a disappointment

-emo

TwistedTwigleg

@SeaFishelle said: I'm not really much of a reader, to be honest. I find it hard to focus on words. I wish that weren't the case, and I've heard people say that after a while the words disappear and you're in a new world. And while I've had that happen to me in books (I really liked the Halo: Fall of Reach novel), it's few and far between. Maybe I just need to find good writers...

Nothing wrong with not being much of a reader! Personally I've found very few books that pull me in enough for the words to fade away enough so I don't notice them, so I totally get what you're saying.

I've also read Halo: Fall of Reach! I really like reading it, as well as reading the books following Kurt and his team of Spartans.

@Megalomaniak said: I can definitely look into adding custom stylesheet choice for a dark theme once I'm done with the new default.

That would be great! I'm okay with just the default theme if adding custom stylesheets turns out to be hard and/or a lot of extra work. Just having a new theme is a huge improvement :)

Last book I read was Ready Player One, which I loved....but it sure made the movie a disappointment

Neat! I haven't read the book or seen the movie.

With a few exceptions, I have found most movie adaptations of books are rather lack luster as they generally stray from the material in the book.

Megalomaniak

Easy way out would be to write a simple userstyles.org script and use a browser plugin to override the colors of the default theme. I'm basically ~~stealing~~ ahem borrowing the variables from the godotengine.org style.css so it should be really easy to-do. ;)

emo10001

@TwistedTwigleg said:

Neat! I haven't read the book or seen the movie.

With a few exceptions, I have found most movie adaptations of books are rather lack luster as they generally stray from the material in the book.

Yep...and this definitely holds true. I'm not that much of a reader either, but this book did pull me in. And I should have known better at the movie theatre :wink:

-emo

Megalomaniak

@emo10001 said:

@TwistedTwigleg said:

Neat! I haven't read the book or seen the movie.

With a few exceptions, I have found most movie adaptations of books are rather lack luster as they generally stray from the material in the book.

Yep...and this definitely holds true. I'm not that much of a reader either, but this book did pull me in. And I should have known better at the movie theatre :wink:

-emo

On that note I'm a bit concerned about the NetFlix Witcher series, but at least they promised to make it an adaptation of the books and not video games(cause we all know how video game adaptations go).

SeaFishelle

Netflix book adaptations have so far come out pretty great. The Series of Unfortunate Events miniseries is fantastic, fitting the tone and style of the books much better than the Jim Carrey movie did.

emo10001

@SeaFishelle said: Netflix book adaptations have so far come out pretty great. The Series of Unfortunate Events miniseries is fantastic, fitting the tone and style of the books much better than the Jim Carrey movie did.

That's a good point. It's easier to say truer to a book, especially a book series when you can spread it out over a 10-15 hour series.

-emo

emo10001

Took a break from the 3D creation world this weekend. Took my boys fishing...caught, cleaned, cooked (well, my wife cooked) and ate the fish. Delicious!

My daughter had a dance recital. She is awesome and full of grace.

Was a good weekend.

Back at it tomorrow!

-emo

SeaFishelle

I took part in a game jam over the last two weeks, and actually finished and entered my project. It was amazing! I can't believe I actually FINSIHED something for once!!

emo10001

@SeaFishelle said: I took part in a game jam over the last two weeks, and actually finished and entered my project. It was amazing! I can't believe I actually FINSIHED something for once!!

Nice! Do we get to see?

-emo

TwistedTwigleg

Hey guys!

In a little over half a hour (as of when this was written) Godot's official community game jam will be starting! Game jams are great for making project/prototype games around a theme with other Godot users.

You can find the jam page here. I think this jam runs for 3 days, and there should then be a voting period after that. The last Godot game jam looked like a lot of fun, so I'm pretty excited for this one! I'm hoping the theme will be interesting and I'll actually have a decent idea on what to make :sweat_smile: (assuming I can find the time to enter the jam)

Edit: Well, the theme is temperature... Hmm... I think I have a general idea of what I am going to do :smile:

SeaFishelle

Well, that's over now... xD

Anyways, my PC is sick. But I'm hoping to jump into game development once it's back online.

TwistedTwigleg

@SeaFishelle said: Well, that's over now... xD

Yeah. Sorry about the late notice! I would have posted about it earlier, but I totally forgot about the jam it until an hour before it started, in which case it was a little late.

Anyways, my PC is sick. But I'm hoping to jump into game development once it's back online.

That stinks. Best of luck getting the PC back and ready to go, hopefully it will not be too difficult.

Megalomaniak

What's it come down with?

SeaFishelle

@Megalomaniak said: What's it come down with?

Fixed now, but here's a rundown: (TL;DR below)

One day, i get home to see it sitting in BIOS. Weird, but I've seen it before, particularly after a power outage. And it was REALLY windy that day; figured a transformer went down for a bit and knocked the thing out. So I tell it to boot into Windows. It then boots, but back into BIOS. Huh? Tried again, back into BIOS. This is odd...

Looked at the clocks, they were all accurate. No power outage today. Uh-oh.

Started doing some research and, after finding a lot of fear-mongering "YOU HAVE A TROJAN!!1!" articles, I turn it off and let it rest for a bit. I boot it up later and lo and behold, it's back into Windows. Thinking it's fixed, I go to bed. Wake up, and it's in BIOS again, caught in a boot loop. Damn it. So I turned it off and went to work. Got home, and turned it on. Was on it for a few hours when it suddenly BSOD'd on me before BIOS-looping, finally giving me an error code to figure out: critical_process_died.

Turns out, Windows kinda gave up on its registry processes and decided to tell me to F myself. The only fix was a full reinstall, which took me like a week because of all the backup-shuffling I had to do with my relatively tiny external drive. But finally, I got a fresh Win10 booted up, important files in two extra places (a backup PC and a Google Drive), and thus far, no BSOD.

TL;DR: My 3.5-year-old Windows install got sick of looking at its registry and resorted to shunting itself into BIOS loops, forcing a total reinstall.

Megalomaniak

What does the disk's S.M.A.R.T. info tell you?

BinaryOrange

@SeaFishelle said:

@Megalomaniak said: What's it come down with?

Fixed now, but here's a rundown: (TL;DR below)

One day, i get home to see it sitting in BIOS. Weird, but I've seen it before, particularly after a power outage. And it was REALLY windy that day; figured a transformer went down for a bit and knocked the thing out. So I tell it to boot into Windows. It then boots, but back into BIOS. Huh? Tried again, back into BIOS. This is odd...

Looked at the clocks, they were all accurate. No power outage today. Uh-oh.

Started doing some research and, after finding a lot of fear-mongering "YOU HAVE A TROJAN!!1!" articles, I turn it off and let it rest for a bit. I boot it up later and lo and behold, it's back into Windows. Thinking it's fixed, I go to bed. Wake up, and it's in BIOS again, caught in a boot loop. Damn it. So I turned it off and went to work. Got home, and turned it on. Was on it for a few hours when it suddenly BSOD'd on me before BIOS-looping, finally giving me an error code to figure out: critical_process_died.

Turns out, Windows kinda gave up on its registry processes and decided to tell me to F myself. The only fix was a full reinstall, which took me like a week because of all the backup-shuffling I had to do with my relatively tiny external drive. But finally, I got a fresh Win10 booted up, important files in two extra places (a backup PC and a Google Drive), and thus far, no BSOD.

TL;DR: My 3.5-year-old Windows install got sick of looking at its registry and resorted to shunting itself into BIOS loops, forcing a total reinstall.

I highly recommend running several disk checking programs. It sounds like you could have faulty sectors, a very similar thing happened to me a few years ago with a barely one-year-old 3TB Seagate HDD that I paid almost $200 for. Of course it happened just after the warranty on it expired, too!

I don't remember what I used, but I think I had a Ubuntu live DVD sitting around and just popped that in and used whatever disk checker program was preloaded on it. Sure enough, about half of my drive had faulty sectors, and whenever Windows would tr to do anything in those sectors it would cause a BSOD or other crashes.

SeaFishelle

@BinaryOrange said:

@SeaFishelle said:

@Megalomaniak said: What's it come down with?

Fixed now, but here's a rundown: (TL;DR below)

One day, i get home to see it sitting in BIOS. Weird, but I've seen it before, particularly after a power outage. And it was REALLY windy that day; figured a transformer went down for a bit and knocked the thing out. So I tell it to boot into Windows. It then boots, but back into BIOS. Huh? Tried again, back into BIOS. This is odd...

Looked at the clocks, they were all accurate. No power outage today. Uh-oh.

Started doing some research and, after finding a lot of fear-mongering "YOU HAVE A TROJAN!!1!" articles, I turn it off and let it rest for a bit. I boot it up later and lo and behold, it's back into Windows. Thinking it's fixed, I go to bed. Wake up, and it's in BIOS again, caught in a boot loop. Damn it. So I turned it off and went to work. Got home, and turned it on. Was on it for a few hours when it suddenly BSOD'd on me before BIOS-looping, finally giving me an error code to figure out: critical_process_died.

Turns out, Windows kinda gave up on its registry processes and decided to tell me to F myself. The only fix was a full reinstall, which took me like a week because of all the backup-shuffling I had to do with my relatively tiny external drive. But finally, I got a fresh Win10 booted up, important files in two extra places (a backup PC and a Google Drive), and thus far, no BSOD.

TL;DR: My 3.5-year-old Windows install got sick of looking at its registry and resorted to shunting itself into BIOS loops, forcing a total reinstall.

I highly recommend running several disk checking programs. It sounds like you could have faulty sectors, a very similar thing happened to me a few years ago with a barely one-year-old 3TB Seagate HDD that I paid almost $200 for. Of course it happened just after the warranty on it expired, too!

I don't remember what I used, but I think I had a Ubuntu live DVD sitting around and just popped that in and used whatever disk checker program was preloaded on it. Sure enough, about half of my drive had faulty sectors, and whenever Windows would tr to do anything in those sectors it would cause a BSOD or other crashes.

Your advice checks out solidly. The darn thing told me to F myself soon after the reinstall, even BSODing during chkdsk. Decided to just give up and buy new drives. Replace both, since I couldn't be completely sure which one was okay. Likely the Windows one, but most of my crashes occurred while accessing things on the other drive.

On the plus side, I got an excuse to start fresh on filespace, as well as upgrade my 1TB HDD to 2TB. All in all, a good thing. If this happens again in the next week or so, I'll point fingers at the CPU. Let's hope it doesn't come to that.

BinaryOrange

@SeaFishelle said:

@BinaryOrange said:

@SeaFishelle said:

@Megalomaniak said: What's it come down with?

Fixed now, but here's a rundown: (TL;DR below)

One day, i get home to see it sitting in BIOS. Weird, but I've seen it before, particularly after a power outage. And it was REALLY windy that day; figured a transformer went down for a bit and knocked the thing out. So I tell it to boot into Windows. It then boots, but back into BIOS. Huh? Tried again, back into BIOS. This is odd...

Looked at the clocks, they were all accurate. No power outage today. Uh-oh.

Started doing some research and, after finding a lot of fear-mongering "YOU HAVE A TROJAN!!1!" articles, I turn it off and let it rest for a bit. I boot it up later and lo and behold, it's back into Windows. Thinking it's fixed, I go to bed. Wake up, and it's in BIOS again, caught in a boot loop. Damn it. So I turned it off and went to work. Got home, and turned it on. Was on it for a few hours when it suddenly BSOD'd on me before BIOS-looping, finally giving me an error code to figure out: critical_process_died.

Turns out, Windows kinda gave up on its registry processes and decided to tell me to F myself. The only fix was a full reinstall, which took me like a week because of all the backup-shuffling I had to do with my relatively tiny external drive. But finally, I got a fresh Win10 booted up, important files in two extra places (a backup PC and a Google Drive), and thus far, no BSOD.

TL;DR: My 3.5-year-old Windows install got sick of looking at its registry and resorted to shunting itself into BIOS loops, forcing a total reinstall.

I highly recommend running several disk checking programs. It sounds like you could have faulty sectors, a very similar thing happened to me a few years ago with a barely one-year-old 3TB Seagate HDD that I paid almost $200 for. Of course it happened just after the warranty on it expired, too!

I don't remember what I used, but I think I had a Ubuntu live DVD sitting around and just popped that in and used whatever disk checker program was preloaded on it. Sure enough, about half of my drive had faulty sectors, and whenever Windows would tr to do anything in those sectors it would cause a BSOD or other crashes.

Your advice checks out solidly. The darn thing told me to F myself soon after the reinstall, even BSODing during chkdsk. Decided to just give up and buy new drives. Replace both, since I couldn't be completely sure which one was okay. Likely the Windows one, but most of my crashes occurred while accessing things on the other drive.

On the plus side, I got an excuse to start fresh on filespace, as well as upgrade my 1TB HDD to 2TB. All in all, a good thing. If this happens again in the next week or so, I'll point fingers at the CPU. Let's hope it doesn't come to that.

If it were the CPU, you would almost certainly have other warning signs.

I recommend not purchasing a Seagate drive, also. :tongue: Western Digital all the way! Samsung for SSDs.

I've just never had good luck with Seagate drives, and when that last one of mine kicked the bucket I just stopped trying to use anything from them. If you can, try to get a Western Digital Black drive - they're super solid and very quick read/write times for a standard HDD.

« Previous Page Next Page »