Ridge Batty

Members
  • Content count

    6
  • Joined

  • Last visited

  1. After wrestling countless hours with a problem (as you do) I came to the conclusion that ShaderMaterial is broken in 3.0. More accurately, I can't get texture lookups to work in vertex shader. But they do work in Babylon 2.5 Add this line in any vertex shader and it wont compile: vec4 test = texture2D(textureSampler, uv);
  2. For the life of me, I can't find a setting which adjusts camera movements with current frame rate (automatically adjusting speed, inertia, turn rate). Camera which either warps or bogs down depending on where you look at is simply unacceptable in any application, let alone games. Maybe it's too obvious but in any case I need some help here.
  3. Ok, managed to solve it (just) before i ran out of coffee. Lesson for everyone using Blender & BabylonJS: do NOT NEVER EVER scale meshes in object mode.
  4. Hello again.... i tried to make a simple animation in Blender to understand how skeletons/bones work in Babylon... and of course, the bottom fell out. it's just a drop dead simple bending cylinder with two bones and three key frames. i can't understand why it doesn't render correctly. i believe it's just me and my lack of knowledge, but nevertheless, i need some guidance. here's the animation: http://aeon3d.fi/test/anitest1.html it's just a simple dual viewport scene, one camera set up at left and second cam at front of the model. everything loads & works ok, no errors and such -- but the animation just looks substantially different than in the original blender file: http://aeon3d.fi/test/mdl/items/bend.blend would be nice to know what's going on.
  5. Very good. But I still must note that it's a bit unclear by looking at the documentation only.
  6. hello there, since this is my first post: kudos to deltakosh et al for this great work. my question is, how can i add custom attributes (buffers) to my shaders? it seems like normals, positions and uv's just magically surface when needed - yes, they're quite cleverly integrated and hidden from the developer. now i know i can cheat the system and use for example normals to send additional data to my vertex shader... but then i can't use the normal data for their original purpose anymore =p i don't want to read and understand the source code... because that is not what you're supposed to do when using a framework. if i wanted to do that, i would write my own low level framework. and -- for the life of me i can't find the info from the documentation. can anyone at least point me to the right direction?