MOAR Converter problems.

OK. so now I'm able to get all the right data to print to the screen.  Theoretically it should've meant smooth sailing form there. Not the case. It seems I'm having problems writing the data to the file. It could also be a problem with the data itself but I'm not entirely sure.

Originally I had been allocating structures dynamically  and writing the vert data to these structures, then writing the structures out to file. The dynamic calls were causing problems with my use of sizeof() so in order to get it just to work I hard coded a couple of things in so I can get the structures up there.  I've written this data to file and even been able to parse it on the other side in my graphics manager. I had to create the object in the graphics manager which required a bit of copy and paste work from the pyramid structures. When I compile my graphics engine I can only see half of the frigate and parts of the polys I can see are a bit off. I'm still not sure what's causing the problems. I'll have to keep debugging.

-A

UV problem fixed

Well I discovered my UV problem.  I was printing with %d instead of %f.  WOW.   I really hope these silly problems go away as I gain more experience in programming. But at least it didn't take me long to figure this out. Now I can move on to putting these values into some vectors and structs and seeing how they turn out.

-A

Converter Troubles

So I've walked through what we've done in class. I think I have the general idea but I'm running into problems. If I can get the right values to print out that should mean I can put them in my struct for my VBO. Should be a piece of cake, but I'm having two major problems.

First,  I'm not exactly sure where I should be writing the code to make this happen.  The print statements I'm making are in DisplayMesh, like we did in class but it feels inappropriate to put everything there. I'm thinking about just creating a new .cpp file and doing the work there. I'll have to make sure I use all the same includes and mimic some of the loops and variable initializations.

Second,  I've figured out how to get the control points mapped out so I can get the coordinates and the norms from that.  I'm having trouble figuring out how to get the UV coordinates to print. It looks to me like there is a large switch statement dependant upon a couple of different modes. I'll have to continue to mess around with this until I get it figured out.  I think I'll scour a couple of other blogs and maybe even pose the question on the boards if I don't find anything soon.

back to work!

LIU sucks

more trouble with the archiver.  I had a little skype session with Ben tonight about it and we still couldn';t figure it out. He posted his code up in the common directory to lend me a hand. I just took a good look and I feel like I'm doing the right thing here. It's weird because when I make my FindFirstFile look like his I get squiggled at. I scoured my project settings again just to be sure and I just can't figure it out. I'm turning in for the night. I'll be headed to the lab before class tomorrow to see if maybe my machine is the problem. If so I've spent hours staring at this thing in futility. Let's hope that my lab work tomorrow gets the job done.

-A

YESSS! LOOK WHAT I HAVE CREATED!

So if you can't tell from the video I'm really riding the high of success right now.

It took me quite some time and I ran into many problems but I finally got my VODKA program to pass all of it's tests. A large number of the problems I ran into had to do with the project properties. I feel like I know those things backwards and forward after last quarter, but somehow I still manage to forget one or two almost every time I start back up.  For some reason it also seems that when i move to a new workspace I sometimes lose some of these settings. I'm not sure why this happens.  From here on out I'm going to try and check all of those settings as I start a new project rather than half way through so that I know I'm not missing something.  It might also be handy to come up with some sort of a check list so as not to forget.

Now it's time to move on to LIU.  I feel like I understand this one rather well conceptually so i think I'll be OK. (The famous last words of an over-confident programmer.)  What I think I've learned from VODKA should really work out to my advantage. Create a header, write it to a file and then throw my chunks in there. I'll be using the method we discussed in class to find the appropriate files and away we go.

-A

ugh. i hate running into trouble.

So I've been trying to get started on these programming projects here and I'm hitting barrier after barrier. I really thought I'd be able to just get up and running after last quarter considering we only had a week off.

My biggest trouble to start was with perforce. I wasn't very familiar with how to branch it off and so instead I just set the workspace inside. I've finally got it working and it shouldn't be a problem from here except that because it is inside of my previous workspace I think the folder naming might get confusing.

Now that I've got my files downloaded one of the first things I did was load up the achiever unit test and give it a build.  the build came down without failing any tests, but running it was a different story. Visual studio told me it was unable to start the program. I'm not exactly sure what this means or how to go about fixing it.  I think for now I'm going to try and take a closer look at the unit tests and try to plan out how I'm going to tackle this problem.

I'm a little worried about some of the structure involved here. We talked about our program calling other executables (VODKA and LIU) and I'm not really sure what that's going to require. I'll certainly be asking more about this in class on Thursday.

Back to the grind.

-A