• Content count

  • Joined

  • Last visited

  1. Oh boy!! Thanks so much! It was actually not the view, but the perspective one! I was erroneously recalculating it each frame (why?! lol), and more over, recalculating it with a different field of view (PI/4) than the camera one (PI/3)!   So your suggestion made me check the matrices code & find the mistake. Now it works like a charm!! So thanks a ton!!! :)   Synth
  2. hi, thanks for your answer. I'm not sure I understand what you mean. I arbitrarily set the position of it, according to where I want it to be: int i=0; sprite.vertexPositionNormalTexture[i++] = new VertexPositionNormalTexture(sprite.position, sprite.normal, new Vector2(0, 0)); sprite.vertexPositionNormalTexture[i++] = new VertexPositionNormalTexture(sprite.position, sprite.normal, new Vector2(1, 0)); sprite.vertexPositionNormalTexture[i++] = new VertexPositionNormalTexture(sprite.position, sprite.normal, new Vector2(1, 1)); sprite.vertexPositionNormalTexture[i++] = new VertexPositionNormalTexture(sprite.position, sprite.normal, new Vector2(0, 0)); sprite.vertexPositionNormalTexture[i++] = new VertexPositionNormalTexture(sprite.position, sprite.normal, new Vector2(1, 1)); sprite.vertexPositionNormalTexture[i++] = new VertexPositionNormalTexture(sprite.position, sprite.normal, new Vector2(0, 1)); sprite.vertexBuffer.SetData(sprite.vertexPositionNormalTexture); For the moment it's static: I'm not translating, rotating or scaling it during gameplay (i'm just setting it's size in the VS). "I would scale by width and height after the transform" - what do you mean? After the camera transform in the VS? If I do that, it will even be worse, as it's going to be camera-oriented i think : will always face the camera & move together with it.   I can be completely wrong though, I'm not in my brightest days :)
  3. Hi guys,   it's been long since the last time I worked on my project, so my question may be silly: I've implemented support for sprites (2D images) in my 3D engine. In this case, I don't need the sprites to face the camera, but to remain in their normal position & rotation, as any other 3D object (I think it's called "world-oriented billboard").   I've achieved this, but there's a problem: when I move the camera, the sprite will slightly move as well (it's not an optical illusion, it's really moving). I'm almost sure there's something missing in my shaders, although I cannot get to understand why this is happening. I've checked several times the HLSL & I cannot find anything. Also checked the vertex declaration & I find nothing.   (I think the erroneous translation may be the camera's delta in the opposite way: you 'look' up in a 10º angle : the sprite moves down in a 10º angle. Although I'm not sure it's exactly like this, it may be something about it).   I attach HLSL Vertex Shader code & images:  VS_OUTPUT output; // Calculate the position of this billboard vertex. float3 position = input.Position; position.x+=(input.TexCoord.x) * width; position.y+=(input.TexCoord.y) * height; // Apply the camera transform. float4 viewPosition = mul(float4(position, 1), View); output.Position = mul(viewPosition, Projection); output.TexCoord = input.TexCoord; // Compute lighting. float diffuseLight = max(-dot(input.Normal, LightDirection), 0); output.Color.rgb = diffuseLight * LightColor + AmbientColor; output.Color.a = 1; return output; [sharedmedia=gallery:images:4303] [sharedmedia=gallery:images:4304] Do you think you can help me with this one? Thanks so much!   Synth
  4. My XNA Game Project - Issues

    Here I store captures of issues I face while developing my project which may be useful to show in order to get some help from forum members as well as to help others to solve similar problems.
  5. Collision - BoundingSphere vs BoundingBoxes Corners

    Thank you, I think the case of the sphere completely inside the box is almost impossible (the wall should be very thick & the player should move very quickly), but I'll analize the other case together with the info you linked. It seems pretty much interesting. Thanks again, Synth
  6. I'm also not sure what you mean, but I don't know any "technology" that will make this for you (if with tech you mean libraries, programs or prebuilt stuff). Basically you have to create a project (a program) in a specific programming language (within a particular development interface like "Visual Studio" for example). It will control the logic of your charactes (also created in there by yourself). You create the visible models in a (for example) 3D / 2D program to later import them in your project & control them logically. I guess you have to program all the possible actions & as the guys here said you may randomize & trigger them, or trigger them according to decisions on what is happening. For example, develop a "run" action (an animation made in a 3D/2D animation software; the actual movement: vectorial translation of the character in a programming language, etc), then a "walk", a "stand", etc. Get a random number & according to it, make one character walk, another, run & so on. For dialogs you should check about "decision trees". For different states & activities you may like to read about "UML State Machine", "UML Activity diagrams": [url=""]http://en.wikipedia....L_state_machine[/url] [url=""]http://en.wikipedia....ctivity_diagram[/url] There's a looooot to implement & it's definately not a matter of 2 or 3 weeks. For development tools I like to use C# and XNA. I also like to build the AI by myself, always with the help of the pros that have previously answered you here. Hope I gave u some light. Cheers, Synth
  7. Hi everyone, I'm working in XNA (C#), & after successfully making my character slide along walls (character represented as a BoundingSphere & wall as a BoundingBox) I've been strugling to solve the well known corner problem. I've been decomposing the BoundingBox of the wall (AABB) into Planes in order to check which one was hit, descard the further ones, try to work with normals & push the player somehow away from the corner direction (in case it hits the outer part of a corner). The problem is that there are plenty of different possible situations... I manage my walls as BoundingBoxes, & each wall is one of them. So in a corner there are 2 BoundingBoxes which come very close one to the other. So there are many planes (outer & inner) that may be hit, from both BoundingBoxes. It's actually very difficult to manage many planes of many BoundingBoxes & get an algorith (which works for inner corners: you are indoors, & outer corners: you out outdoors). I'll try to show my issue in a pic (seen from above), & I'd like you to help me in thinking about a solution. Is it a mistake to decompose the BB into Planes & work with them individually? (maybe I'm complicating things too much...) May I cast rays...? May I treat the corners with a fixed resolution? I hope you can guide me somehow, I've really spent a lot of time thinking about solutions & they always match a new case in which they won't work. Thank you so much, Synth P.S.: Oh, I also have an annoying problem in which when I slide along a wall I can see the interior of the "room" (I see across the wall) & I'd like to get rid of this in an elegant way...!
  8. Hi Matt, thanks for your answer, the info you gave me tempted me to dig more on matrices & now I understand them much better [img][/img] After I read more, played with matrices & applied the Matrix.CreateWorld, the problem persisted anyway. I spent all the afternoon double & triple checking everything & I wasn't able to find anything wrong in the code! So I created the model over & over again... I recorded a video showing the problem & I was already writing here a new message when I had an insight...: "am I exporting the model left handed...?" Daaaaaaamn that was the problem! [img][/img] Half of me felt as a dumb @ss, but the other half shouted: "YEEEEEEAAAH!!" hehe, so it works like a charm! I actually want to thank you for pointing me out this info (I didn't know how matrices were storing this data) as now I understand it & it helps me for future usages! Cheers, Synth
  9. Hi everyone! I'm having a little issue when trying to decompose a view matrix: I basically have a spot light which works fine. I added an alpha blended cone model to create a light volume effect. It looks allright & everything is fine except its rotation. I thought I could probably create a view matrix for the light (with position & target) & decompose it to get an automatically made rotation matrix (to apply to the cone & get the same rotation as the light). But when I decompose it, the values I get don't seem to be correct. The translation matrix is not working for me & the rotation doesn't seem to be right. I wonder why is this happening &, in case I cannot achieve it like this, how may I get a rotation from a source & a target point in 3D (this [url=""]http://www.chriskugl...en-two-vectors/[/url] didn't work for me, maybe I'm doing smth wrong, but I don't know...) Here's how I create the view matrix & then I decompose it: [source lang="csharp"]light.view = Matrix.CreateLookAt(light.position, myPlayer.animatedModel.position, Vector3.Up); bool deco=light.view.Decompose(out scaleView, out rotationView, out translationView);[/source] I also attach a pic showing the light (following the player) & the cone (moving in a way that sometimes matches the light movement but it's not right). The light diameter is exagerated to illustrate the case, the idea is that the cone is scaled depending on the light diameter, I just have to tweak it a bit somehow to match). The cone doesn't seem to move in X, it moves in Z following the light movement but not matching it. It moves in a very restricted range & X movement seems to be rendered in Z. Thanks in advance, Synth P.S.: I'm not sure I'm posting this in the right forum because it mixes math, graphics & xna elements, so forgive me if I'm wrong. Thanks.
  10. Good to know that! Thanks a lot, that was an ultrasonic speed answer!! [img][/img]
  11. Hi, I've been programming in C# for a long time & one thing I'd love to have there (optionally) are pointers. I've been developing a game project for several years, & I usually declare attributes in my classes in order to store other handy objects. For example, I've created a custom ModelMesh in which I store it's parent (container) Model: class ExtendedModelMesh() { -Model theModelWhoContainsMe; } I do this for example to be able to access easy & quickly to the model's position, rotation, scale attributes & some other things. My question is: Is it a performance killer? (in this particular case I store the same model along all it's meshes (imagine 150 meshes per model). Is it not only eating a lot of memory but also slowing down things when fetching up the model? Thanks a lot, Synth
  12. XNA 3.1 - HLSL Params Bottleneck

    Thank you very much, I will definatelly test it as you explain, starting with PIX. I'll also double check the VSync & fixed time step. Thanks a lot for all the info & the fast response! Synth
  13. Unbelievable!! All of this in javascript?! Congratullations, it's amazing!!! You are an animal, what a work!! hehe! Do u use Silverlight? Canvas? I read that in Silverlight is posible to apply some trimmed pseudo XNA (not being able to load 3d models). What technology do u use? Cheers, Synth
  14. Hello, I think I may be having a bottleneck when passing parameters to my HLSL effects. I'm using Deferred Rendering & each model knows how to draw itself (has a draw method). I tell each model from outside which technique to apply or if to use a specified technique within the model (previously set in loading time). They always use the effect set by my custom model processor. I arranged everything so the shadowing technique & the normal drawing technique are inside of the same effect file, so i always use the same effect, the same draw method & the same parameters: depending on the technique I send to the unused params "Matrix.Identity" for example (just to send something & let it work). But I think that may not be very good... I'm thinking on splitting the effect files, & specifying them during runtime (just like I do with the Techniques). But the problem is the parameters in the draw method of the model. Some time ago I was having a desing in which the models didn't know how to draw themselves & were drawn by a "Deferred Renderer", a "Shadow Renderer", etc. I keep some of this design, but the final "draw" thing is inside of each model (even I think it was a better design, I changed it because of compatibility with octrees, where you don't know what u put inside, but they just "draw" themselves). So... how do u advice me to face this problem? May the bottleneck actually be there or may I be completely off aim? (is it possible to profile this kind of thins in PIX? Do u advice me any other, maybe better, software?) Thanks a lot Synth
  15. Trying to program a game...

    [quote name='Sly Cat' timestamp='1321831575' post='4886012'] I'm trying to program a computer game. For example, the game gives a robot a random amount of health and you get a weapon which deals 100 damage. You can choose to attack or retreat (quit) after each attack. Now so far I've only been programming using C++ in the black console screen and I wanted to know how I can take that program and make characters and make a real game. It doesn't have to be anything fancy it can even be 2D... I just wanted to know how. [/quote] Well, you could try DirectX (c++) or XNA (c#, which is similar to C++ without pointers & some other stuff). Here you can find nice tutorials which lead you from the beginning: [url=""][/url] (you can find XNA & DirectX tutorials on the right part of the page. You can also compare & see that it's not so different one from the other). XNA is a wrapper around Direct X which lets u make some things easier. Direct X is a multimedia component which includes solutions for you to handle networking, sounds, graphics, inputs, etc (so u don't have to write evrth in assembly, like in the old times when loading a simple bitmap, nor handling palettes & this kind of stuff). Appart from that, DirectX (& XNA in consecuence) work directly with hardware, which makes things faster: If you load a bitmap & work with it in a typical Windows Form, you won't get good timing results: movements will be slow & will flicker, as there are many abstraction layers beneath Windows Forms. On the other hand, DX & XNA lay almost over the hardware. Hope this helps! Synth P.S.: there are more options, like OpenGL, or others, but be careful when choosing: it's not all about graphics, but input, sound, etc. etc. so be sure this libraries cover this areas as well.