Author Topic: what p64 does  (Read 400 times)

ponut64

  • Full Member
  • ***
  • Posts: 180
  • Karma: +13/-0
    • View Profile
what p64 does
« on: August 20, 2018, 09:22:52 pm »
So I'll start a thread, I guess, instead of spamming the help forum :)

https://youtu.be/Y3nbalLUi0k

Anyone got clues about delayed audio? Might the B-Bus be saturated, causing a command delay?

If anyone wants to build/look at the code, here it is:
http://www.mediafire.com/file/9d3draeitk98ot0/proj_82018.zip/file

And yes, most of my posts are going to be about problems, as is typical...
« Last Edit: August 20, 2018, 09:49:48 pm by ponut64 »

ponut64

  • Full Member
  • ***
  • Posts: 180
  • Karma: +13/-0
    • View Profile
Re: what p64 does
« Reply #1 on: August 21, 2018, 04:23:46 pm »
There was never any delay.. it was just the capture device being the garbage it is...  ::)
https://youtu.be/0TOLTnLY5YE
« Last Edit: August 21, 2018, 06:35:16 pm by ponut64 »

ponut64

  • Full Member
  • ***
  • Posts: 180
  • Karma: +13/-0
    • View Profile
Re: what p64 does
« Reply #2 on: September 02, 2018, 06:05:41 am »

Cerv3ro

  • Newbie
  • *
  • Posts: 7
  • Karma: +1/-0
    • View Profile
Re: what p64 does
« Reply #3 on: September 06, 2018, 12:01:21 am »
Great job, did you know something about developing before?. Do you have an idea of what to create or are you only testing?.

ponut64

  • Full Member
  • ***
  • Posts: 180
  • Karma: +13/-0
    • View Profile
Re: what p64 does
« Reply #4 on: September 06, 2018, 02:20:16 am »
1. I've never developed software before.
2. I've never programmed in the C language before. I did have some training courses on C# and C++ in Microsoft Visual Studio, but this did not output an executable.
3. I've never made development tools before. As I see it this is the true mark of a game development programmer. XL2 and Jo made the development tools.
4. I have had experience working in Unreal Engine, Torque, CryEngine, and TRIBES before as either making simple mods or making maps. Never finished anything but relatively simple maps.
5. My 3D modelling experience comes from making 3D printed objects, such as detailed figurines or mechanical objects. Like, for instance, an entire computer case.
That is a vastly different field because there one is required to make a manifold object. Video games carry no such requirement and often non-manifold objects consume less polygons.

6. As far as what game to make, my philosophy is what I can program is what should define what I can and will make.
Following that, I am going to do testing as far as I can until I feel as if I have programmed enough mechanics to make a satisfactory video game.

7. I work slowly.

ponut64

  • Full Member
  • ***
  • Posts: 180
  • Karma: +13/-0
    • View Profile
Re: what p64 does
« Reply #5 on: September 07, 2018, 08:43:36 am »
In stumbling about with true box-to-box collision detection (rather than only points), I stumbled on an alternate way to test a point against a normal.
It's helpful to share this, because it's basically 16-bit.

Code: [Select]
Sint32	pt_col_plane(Sint16 planept[XYZ], Sint16 ptoffset[XYZ], Sint16 normal[XYZ], Sint16 offset[XYZ])
{
//Using a NORMAL OF A PLANE which is also a POINT ON THE PLANE and checking IF A POINT IS ON THAT PLANE

//the REAL POSITION of the normal, which is also a POINT ON THE PLANE, needs an actual position. WE FIND IT HERE.
Sint16 realNormal[XYZ] = {normal[X] - offset[X], normal[Y] - offset[Y], normal[Z] - offset[Z]};
Sint16 realpt[XYZ] = {planept[X] + ptoffset[X], planept[Y] + ptoffset[Y], planept[Z] + ptoffset[Z]};

//the DIFFERENCE between a POSSIBLE POINT ON THE PLANE, and a KNOWN POINT ON THE PLANE, must use the REAL POSITION of the NORMAL POINT.
Sint16 pNn[XYZ] = {realNormal[X] - realpt[X], realNormal[Y] - realpt[Y], realNormal[Z] - realpt[Z]};

//The NORMAL of the plane has NO REAL POSITION. it is FROM ORIGIN. We use the normal here.
//If the dot product here is zero, the point lies on the plane.
       //The dot product being negative or positive can be used to determine whether the point has passed the plane.
Sint32 dot;
dot = vectori_dot(pNn, normal);

return dot;
}

If you're wondering what else I would use, its separating axis theorem, which while simple to explain is much more verbose in code so I'll not go into that much more.

 

Sitemap 1 2 3 4 5 6 7 8 9 10 
SMF spam blocked by CleanTalk