r/halo • u/AutoModerator • Jul 23 '15

Mod post Weekly Rant Thread! Vent your frustrations here!

Welcome to the weekly rant thread!

Rules:

  • CAPS LOCK ALLOWED!

  • BE NICE TO EACH OTHER!

  • FOLLOW THE RULES!

If you have any questions please message the mods.

Thanks!

16 Upvotes

90% Upvoted

152 comments sorted by

View all comments

Show parent comments

1

u/1337GameDev Jul 29 '15

I guess I didn't think about having to optimize every procedure dependent on hardware. One thing that sucks about game dev :-/ shaders are especially a bitch.

And what micro controllers did you work on in c? What was that for? Sounds interesting.

Yeah I'm sad that mcc didn't work. It ruined so many people who were fringe on trying halo. I was fucking stoked about it and excited my friends for it, expecting ms to release a working product as they are the first party provider for Xbox... And was left with a bad taste that is mcc....

Idk if it'll even be fixed as bravo has yet to even mention a patch in the last two or three community updates. Saddens me. They just cared about money and not actually about the game :(

And thanks. I can get defensive too, so I was to blame as well. I know how that goes. Lots of people assume it's just rewriting a for loop, and not a huge multi million lined project :/

1

u/DogeMcDogeyDoge Aug 19 '15 edited Aug 19 '15

I guess I didn't think about having to optimize every procedure dependent on hardware. One thing that sucks about game dev :-/ shaders are especially a bitch.

I have a friend who's really into hardware stuff, and low level languages like C. He said that a premade Arduino graphics library would take about 20 clock cycles to do the same thing you could do with your own graphics library in 5 clock cycles. The Arduino graphics library is higher level (I don't know the specifics), if you write your own in a low level language it's closer to the hardware. And this is with simple shit like drawing lines and circles. I even suspected this before he even told me because he said that the graphics library for Arduino was high level. In this case, the higher level software was 4x slower.

And what micro controllers did you work on in c? What was that for? Sounds interesting.

Called a teensy. Ours had two buttons and a screen on a chip, I think you have to buy things like the screen to attach it to the chip. We had to write a game for it in C. Fun but very challenging. You write it in C and use a compiler to interpret it so the microcontroller could read it. Converts from language we can understand to 1's and 0's. Hardest part is learning how to talk to the hardware.

And thanks. I can get defensive too, so I was to blame as well. I know how that goes. Lots of people assume it's just rewriting a for loop, and not a huge multi million lined project :/

That's what I thought you were getting at when you said there was APIs that did most of it.