next »

[Sik]

Well, that explains it =| But absolutely not a single place documenting git pull seems to mention that it doesn't overwrite the files that weren't updated, so of course somebody who doesn't know that sees the message and thinks that it'll undo every change that was made after the last update. Ugh.

Probably better terminology would have cleared up the confusion, but still.

[Geti]

Some reading about how DCVS in general work (even just reading the wikipedia page on git) could probably have cleared that up though The whole idea is that there's no forced, central state, and that operations are generally non-destructive. Revisions are explicitly kept separate until brought together manually.

[Udderdude]

http://tgceec.tumblr.com/post/106626335863/introducing-the-grand-c-error-explosion

[gimymblert]

10 years after learning them I met back with integral with shader stuff, I was so confused where all those dtheta/domega variable come from well it's a notation to bound the integral it mean "nothing" (yeah I KNOW what it mean really), I wasted my time being confused over F*****ing nothing... and now thing are back to simple, I feel stupid now  

[standardcombo]

http://tgceec.tumblr.com/post/106626335863/introducing-the-grand-c-error-explosion

Crazy. As a thought exercise, I try to imagine explaining this competition to a scifi enthusiast from the 60s or something.

[EdFarage]

Wake up with solution in brang.
Sit down to code...
..um.

story of my life
 

[tjcbs]

Ugh. This took way too long to figure out. Who can spot the error?

Code:

   int near =  (filter == TEX_FILTER_LINEAR)   ? GL_NEAREST : 
               (filter == TEX_FILTER_BILINEAR) ? GL_LINEAR  : GL_LINEAR_MIPMAP_LINEAR;

1>.\tgl\texture.cpp(452) : error C2513: 'int' : no variable declared before '='

[gimymblert]

look at the line before

[Quarry]

I've been dabbling around in my collision resolution code for more than an hour now, everything except one tiny detail is working now and I really am out of ideas except this single thing...

[Sik]

Ugh. This took way too long to figure out. Who can spot the error?

Code:

   int near =  (filter == TEX_FILTER_LINEAR)   ? GL_NEAREST : 
               (filter == TEX_FILTER_BILINEAR) ? GL_LINEAR  : GL_LINEAR_MIPMAP_LINEAR;

1>.\tgl\texture.cpp(452) : error C2513: 'int' : no variable declared before '='

...are there any compilers left that still treat 'near' and 'far' as keywords?

Also what kind of naming scheme is that? Nearest filtering definitely isn't linear (linear would mean filtered in one axis but not the other). That's why you hear about bilinear and trilinear but not just linear.

[tjcbs]

...are there any compilers left that still treat 'near' and 'far' as keywords?

Also what kind of naming scheme is that? Nearest filtering definitely isn't linear (linear would mean filtered in one axis but not the other). That's why you hear about bilinear and trilinear but not just linear.

I'm still using VS2008.

You are right, the naming is wrong, I knew something was off when I was typing that. OpenGl does call bilinear GL_LINEAR, as in linear interpolation.

[Sik]

I thought it didn't take them as keywords when not building for 16-bit Windows (and I'm not even sure if VS2008 still supports that). Oh well. But yeah, unless you've seen programming for 16-bit x86 in the past, you're likely to have trouble figuring out that one.

[Boreal]

Trying to implement deferred rendering and OpenGL only wants to render to the first color attachment and the depth-stencil attachment.  No indication as to why.

[surt]

Spent the whole day trying to figure why my events weren't firing.
Basically rewrote code from scratch twice.
Was attaching to event "changed" rather than "change".

[oahda]

why are 90 % of programmers so bad at reading

i've seen people look for a missing semicolon for minutes
and i'm too polite to point it out and make them feel stupid

[ProgramGamer]

I'll answer that for you. They're so absorbed with looking for something at a specific place that they ignore everything else in all other places, including what they might actually be looking for.

[Sik]

Not even that, they keep reading what they thought they wrote, not what they actually wrote. Same deal with buggy algorithms, they try to analyze it like how they think it should work, not like how it actually works. This is also why auditing by all programmers is a good thing, others may have it easier to spot the issue.

i've seen people look for a missing semicolon for minutes
and i'm too polite to point it out and make them feel stupid

They'll feel stupid when they find out the issue anyway, may as well save them the time.

[Schrompf]

Porting my C++ game to Linux. 10+ static libs, another 10+ prebuilt dependencies. GCC unearthes some errors that have been there for 10 years. And it also annoys the heck out of me when insisting on some stupid old C++ specification details that everyone else silently ditched 10 years ago. The two phenomena are probably linked. 

[ProgramGamer]

Not 100% game/programming related, but my parents are insisting on limiting my computer time because, well, they believe that I should find a job in which I can learn buisiness skills such as communication, responsibilities and dealing with unreasonable people. I'm 17. Are they right to do this or just way too worried? I can't think straight because of frustration right now. 

[oahda]

Since when is programming not an employment (why limit it to business?) skill? Get a programming job!