Skip to main content
MANIFOLD
What will be my efficiency* in study programming project?
5
Ṁ1kṀ1.3k
resolved Jun 19
Resolved
YES

I expect the project to take 20 hours. Let's call T the real time spent on the project.

G is the value, corresponding to my final grade/mark. G(A)=1, G(B)=2, ... , G(E)=5, G(FX)=10^10.

This market will resolve to N, where N = 20/T/G. If N>1 then resolves to 100%.

Examples.

If I spend 30 hours and get B: N=20/30/2=33%.

If I spend 10 hours and get D:

N=20/10/4=50%.

If I spend 15 hours and get A:

N=20/15/1 -> 100%.

I will bet, and likely comment my progess.

Market context
Get
Ṁ1,000
to start trading!

🏅 Top traders

#TraderTotal profit
1Ṁ596
Sort by:

I got A.

20/T/A=20/10/1=200%

Resolves to 100%.

9h. Deepfry solved. Interpolation solved itself automatically when i was correcting other bits.

I am commited to present my current version. It is unoptimised, 1 frame per second, but technically I implemented almost everything we studied this semester.

I will do some minor things related to the project (making screenshots for example), so i say 10h is the final number.

8.5h I solved lighting! But it is deepfried. Need to have every vertex to have 2 colors now, its base and its color after reflection being calculated. Feels like an easy fix. Also need interpolation between points, and that might be tricky.

I have 20h before deadline. Code is not optimised, but even at this stage with deepfried colors I can hope for B.

8h. Zbuffer is implemented, but when camera moves distances are not recalculated for some reason.

Scaling of the model is implemented.

Fixed missing triangles.

I messed up the coloring, and they are now fixed. Not responsive to the light, reflections etc.

So, to solve one feature several hours ago i had to centralise camera. I made it so that it rotates around a point. But i forgot, that my lighting-code paradigm works for free-moving camera.

I don't even know how to solve this collision. Maybe i will need to add a ghost camera position to calculate. Complicated...

7h. Working with zbuffer.

6h

Need to add valid coloring (lighting, diffusion, reflections). I have the code for that copied from previous project, but it just draws nothing.

Also need to add controls, to rotate and scale the model

5h. Everything is already so complicated, that even changing the default camera position causes crashes.

I can draw wireframe (due to the camera spawn problems it is difficult to find it in the empty white void), but coloring it is so complicated that it freezes.

Will try to comment out chunks of old code.

4h. Memory reset when opening a new file. Calculating map of normals.

3h. Converting the data into the first intermediate format (will need to convert twice more), calculation of point colors.

Trying to do safely, it is too easy to crash windows while working with api.

2h. Unicode slows me down as it needs its own type of strings in c. Still trying to open a file.

0.5 h. Decided to stick to WinAPI. Did not understand how to install raylib and how it works exactly.

@KongoLandwalker what scale will your project be graded on?

I forgot to tell this part:

Grade is technically not for the project, but for the whole semester.

I had 3 projects before that: 2 perfect, 1 sligthly not. In all 3 cases I was doing a harder things than my classmates were, so I think I got some respect from the teacher. (I was building 3d graphics on a lower level by accessing screen buffer through Windows API, while everybody else used Qt library and its canvas. Here is how my previous project looks https://youtu.be/Va53T9UV_uM?si=5x0jlAagrgLJDwW_ ).

I do not know the scale of the grading. I know, that if the new project does not work, it is FX. If it works, it is A-E.

I might not use Windows API this time. I will likely not use Qt, it creates insanely big projects, which slows down my notebook a lot (1Gb with Qt, compared to 15Mb when using WinAPI).

bought Ṁ1 YES

I plan to start tomorrow.

I have some code from previous project to render triangles i might use, but it was neither optimised, nor universal. (Due to math choices it works only with convex bodies)

Shortly, the program in c++ has to open files in special format and draw rotatable 3d representation of the terrain.

All the graphics have to be programmed up from pixel level.