@Megalomaniak said: The barracuda is a Seagate consumer line. i.e. trash(unless it was a barracuda pro). WD is fine, but Hitachi/HGST is statistically best. No wonder WD was happy to buy them out. Personally if I can't find the Hitachi/HGST drive I'm looking for I go for Toshiba as my fallback.
Oh... Well, at least I have the warranty. :D
@BinaryOrange said:
@SeaFishelle said:
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.
I just bought a Kingston SSD again. The HDD is a Barracuda, which I don't know much about but the guy at the counter seemed to know what he was talking about. In any case, I bought the 4-year warranty plan with this store, so I get free ones if they die again.
@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.
@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.
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.
"I am altering the deal. Pray I don't alter it any further."
I really love the room thing you have going. It reminds me of Four Swords Adventures. Super neat stuff.
I accomplished this in BGE a few years ago. If I remember, I'll look at my old projects when I get home and see how I did it. Being BGE, I of course had to hack it to hell and back to get around the bizarre quirks of the parent/child physics system... Hopefully with Godot's much more straight-forward design, it should be a relatively simple concept application.
@GarromOrcShaman said:
@arthur said: You need to
remove_childbeforeadd_child.remove_childdoes not free node.Now I'm able to parent player (rigidbody) to platform (staticbody) but player does not inherit position. It is bug or my mistake ? How i can make rigidbody inherit position/rotation from static body ?
Manually?
transform += Floor7.transform
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!!
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.
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...
Hey, I did that!
https://blenderartists.org/user_avatar/blenderartists.org/michellesea/120/26107_1.png
I started by using verts and edges to draw a fish-shaped outline, then I extruded them to build a shape out the side.
@Gonoob said: My understanding is that polish is when you have finished product and you only have some finishing touches to do. My understanding is that polish is what you call someone from Poland.
(sorry, I saw the opportunity and I jumped on it. :D)
@Megalomaniak said:
@SeaFishelle said: If you're not going to pay people, you should probably mention that up-front, and not use the "professional trade" tag.
No, pro-bono work is still professional trade.
Oh, my mistake.
Oh so this is just a practice project? Neato! :3
If you're not going to pay people, you should probably mention that up-front, and not use the "professional trade" tag.
And as @TwistedTwigleg said, if you're trying to bring people in on your project, use as much detail as possible. People don't want to work for someone that isn't going to fully explain what they need, because they have no idea what to expect to have to do. Artists need details, especially if you want specific art done.
Cool start! What kind of RPG are you making? Do you have any docs written up yet? What kinds of assets do you have so far, outside of this dude and his lovely field of grass?
@MagicLord said:
Tutorials should be made by the engine team, they are the best skilled to work on those. You are right , there is an FPS tutorial, and this is the only one , while there should be many to showcase how you can do other game genre in Godot, or game starters. Requests about polishing the editor are nice, but the engine features needs polish also.
We've been over this, an engine developer isn't automatically a good teacher.
The "if you made it, you're an expert of it" philosophy is incorrect. Look at eSports games; the developers of any given major game get their butts handed to them by professional teams. Why? Because those teams spend their time practicing the game and learning how to play it, while the teams spend their time writing code, making assets, and doing business things. When they play the game, they don't play it to practice, they play it to make sure it works.
On that same level, look at Godot's documentation. It's a mess. There's a lot of content, sure, but it's unpolished, vague in many areas, and an English grammatical nightmare. That's because it was written by a French engineer who's trying to explain a codebase he's partial to and knows too well to be able to describe to a total newbie.
Imagine having to explain the concept of a chair to an alien that doesn't have legs or knees. Not easy, is it? That's what you're asking the Godot guys to do.
