Jump to content

  • Log In with Google      Sign In   
  • Create Account

FREE SOFTWARE GIVEAWAY

We have 4 x Pro Licences (valued at $59 each) for 2d modular animation software Spriter to give away in this Thursday's GDNet Direct email newsletter.


Read more in this forum topic or make sure you're signed up (from the right-hand sidebar on the homepage) and read Thursday's newsletter to get in the running!


medevilenemy

Member Since 29 May 2005
Offline Last Active Today, 08:11 PM

Topics I've Started

Time for some new headphones

17 March 2014 - 06:01 PM

So, I'm in the market for a new pair of headphones, sub $200 US.  (I prefer closed back, over-ear)  A couple people have suggested the Audio-Technica ATH-M50 or M50x, and I've tried on a pair of M50s... They do sound pretty excellent, though the earcups felt a little small to me.  What do you all think?  I definitely like the nice flatish frequency response, but I'm overall not particularly an audiophile.  Would you suggest trying them, or perhaps there's some alternative that you think would be better?

(I'm also considering stepping it down to the M40x or an equivalent, since they're significantly cheaper)


Unity Raycast issue

16 May 2013 - 08:23 PM

Hi all.  Since my last post, my team has convinced me to switch to Unity3D from my own homebrew engine.  So, I'm in the process of reimplementing some features that I had completed in my engine.  Specifically, automatic doors and ladders.  I'm using a pair of raycasts, one in either direction from the player center (at least, I think its from the player center) to detect appropriate "interactable" objects as follows:

 

Physics.Raycast(thisTransform.position, -Vector3.right, out hit, rayInteractableDistX, InteractableNonGroundMask) for left and

 

Physics.Raycast(thisTransform.position, -Vector3.right, out hit, rayInteractableDistX, InteractableNonGroundMask) for right

 

Where thisTransform is the player's transform.  The problem I'm having is that these raycasts don't seem to work when the player overlaps the target object (ie:  When the player is standing in the middle of the doorframe).  Because one of the ways of exiting climb mode is to not be touching a climbable anymore, this is entirely preventing climbing from working, and seems to cause the door to close on the player as well.

 

What am I doing wrong?


Coordinates on a wedge

20 September 2012 - 06:40 PM

What is a good way to iterate over all the points on and within an arc wedge, given a known center point, start angle, end angle, radius, and grid spacing?
Context: The lighting system for my engine blends arcs into an opaque mask (thus creating areas of visible "light" where you can see through the mask). These lights are defined by the center point of the circle they'd be on, the starting and ending angles of the arc (say, 0 and pi/2), and the radius of the imaginary circle the arc would be on.
The equation for converting a given coordinate from world coords to the coords of the underlying detection system is:
result = (int)(input+1)*100

I could brute-force this easily enough by iterating over angles and then over lines at angle from center to radius, but that would be really inefficient and wouldn't necessarily hit every grid point on the wedge (Unless the iteration over angles was really tight, and that would make it even less efficient).

odd parallax effect

26 June 2012 - 09:59 PM

I've been writing a nice shiny new lighitng system, but have run into a small snag... I can render the new lighting stuff (a texture to which I have drawn an appropriate lighting mask), but when I move my camera, the lights (which are holes punched through an opaque cover) don't seem to move at the same rate as the underlying scene. I use the same camera placement code in the FBO (to make the texture) rendering context as I do in the underlying scene. The only real difference I can think of is that the local Z coords happen to be set up backwards between the two (but that shouldn't have any effect on horizontal camera movement, I think).

The relevant camera code is:

gluLookAt( Position.x,Position.y,Position.z,
ViewPoint.x,ViewPoint.y,ViewPoint.z,
UpVector.x,UpVector.y,UpVector.z);

where ViewPoint = the sum of the Position and ViewDir 3d vectors, ViewDir = (0.0, 0.0, -1.0) (i've tried flipping the z coord for the camera setting in the z flipped FBO context with no apparant effect), and UpVector = (0.0, 1.0, 0.0).

I'm using an ortho projection for both the main scene and the FBO. I tried using gltranslated for the FBO local camera but that seemed to make the problem worse.

Sorry for reposting this, but I see the last one as having 0 views... that seems broken.

glulookat and the case of accidental parallax

23 June 2012 - 12:56 AM

<< Accidental double post! Please delete!>

PARTNERS