[email protected]
Twitter
LinkedIn
YouTube
GitHub
  • Services
  • Blog
  • Repositories
  • GitHub
  • Resume
    • LinkedIn
    • PDF
  • Contact
Product was added to your cart

Cart

Babylon.js course

May 1, 2015Toolsjfadev

Babylon.js It is a complete framework for creating 3D games with the help of HTML5 and WebGL based 100% in JavaScript, developed by programmers from Microsoft. It works properly in Firefox and Chrome and is compatible with the following features:

  • Graphic scenes complete, light, cameras, materials and textures
  • Motor collision
  • Scene selection
  • Antialiasing
  • Engine animations
  • Particle systems
  • Sprites and 2D layers
  • Optimization engines
  • Standard materials at the pixel level
  • Fog
  • Blending alpha
  • Alpha testing
  • Billboarding
  • Full screen mode
  • Shadow maps and maps of variation of shadows
  • Rendering textures
  • Dynamic textures (canvas)
  • Video textures
  • Cameras (perspectives and orthogonality)
  • Cloning of mesh
  • Dynamic meshes
  • Maps of time
  • The scenes of Babylon can become in. OBJ, .FBX, .MXB
  • Exports the Blender

 

Below is a video course well very well explained in Spanish fromOscar Uh Pérez (Develoteca) that gives us all the skills needed to put the hands in the dough.

 

 

Also I leave some interesting tutorials of Julian Chenard to start with Balylon.js in the following link: http://www.pixelcodr.com/

 

More tutorials: http://www.babylonjs-playground.com/

 

Repository

Babylon.js is a powerful, beautiful, simple, and open game and rendering engine packed into a friendly JavaScript framework.
https://github.com/BabylonJS/Babylon.js
3,686 forks.
26,085 stars.
22 open issues.

Recent commits:
  • Fix WGSL vPartIndex redefinition when combining Gaussian Splatting material plugins (#18931)## What & whyThe Gaussian Splatting material plugins —`GaussianSplattingSolidColorMaterialPlugin`,`GaussianSplattingGpuPickingMaterialPlugin`, and`GaussianSplattingDebugMaterialPlugin` — each inject their own `varyingvPartIndex` via `CUSTOM_VERTEX_DEFINITIONS` /`CUSTOM_FRAGMENT_DEFINITIONS`. Attaching more than one to the samematerial declares `vPartIndex` twice, which is a **fatal `redefinitionof 'vPartIndex'` error under WGSL** (the duplicate `@location` varyingsfail to compile, so splats stop rendering); GLSL has the same duplicatedeclaration.This happens in practice whenever, for example, theobject-ID/solid-color plugin and the debug plugin are both attached toone compound splat mesh.## FixAdded a shared `GetPartIndexVaryingDeclaration(shaderLanguage)` helperin `gaussianSplattingMaterial` that emits the `vPartIndex` varyingwrapped in an include guard (`#if !defined(…)` / `#define`). All threeplugins now declare the varying through it, so it survives exactly onceno matter how many part-index plugins are attached.## TestsAdded `gaussianSplattingPartIndexVarying.test.ts`:- helper emits guarded declarations for WGSL and GLSL;- two guarded declarations collapse to one after preprocessing;- control: two unguarded declarations stay two (the regression the fixprevents);- solid-color + GPU-picking combined declare `vPartIndex` once (WGSL +GLSL, vertex + fragment);- debug plugin routes through the shared guard.All Gaussian Splatting unit tests pass (183).Co-authored-by: Raymond Fei <[email protected]>, GitHub
  • Version update 9.27.1, Babylon.js Platform
  • Patch trigger, Babylon.js Platform
  • Add normalized occlusion query visibility API (#18919)> 🤖 *This PR was created by the create-pr skill.*## SummaryAdd a backend-neutral `AbstractEngine.isOcclusionQueryVisible(query)`API for callers that need occlusion visibility without depending onbackend-specific query-result magnitude.- implements the portable visibility contract once as`getQueryResult(query) > 0`- keeps `getQueryResult()` unchanged for existing raw-result consumers- updates Babylon's mesh occlusion path to use the normalized API- documents both the raw and normalized contracts- tests zero, several positive values, and inheritance across the WebGLand WebGPU engine abstractions## Why a separate APIWebGL `ANY_SAMPLES_PASSED(_CONSERVATIVE)` results are effectively GLuintbooleans and commonly appear as `0` or `1`. Babylon's WebGPUimplementation converts the backend `u64` query value with`Number(…)`, so a visible result may be a positive value greater than`1`.Normalizing `getQueryResult()` itself to `0`/`1` or changing its returntype to boolean could break callers that consume the existing rawbackend value. The new method is additive and gives callers one portablevisibility contract without changing that behavior.Callers that only need visibility can migrate from backend-specificresult handling to:“`tsconst isVisible = engine.isOcclusionQueryVisible(query);“`The method belongs on the shared `AbstractEngine` query abstraction, soWebGL and WebGPU inherit the same interpretation. Babylon's own meshpath uses it as the canonical consumer. This PR does not changerender-pass creation or `beginOcclusionQuery` sequencing.## Validation- focused occlusion-query unit tests: 5 passed- `@dev/core` TypeScript compilation passed- targeted Prettier and ESLint passed- repository `format:check` passed- repository `lint:check` passed- repository unit suite: 5,682 passed, 1 expected failure; one unrelatedUMD test hit its 5-second timeout and passed when rerun alone (5/5)- prior devhost validation confirmed runtime registration through thequery side-effect module———Co-authored-by: Copilot App <223556219+[email protected]>, GitHub
  • Stop persisting invalid Nx cache in CI (#18925)> 🤖 *This PR was created by the create-pr skill.*## ContextMonorepo CI jobs have been completing with a silent post-job failurewhile Azure Pipelines saves the Nx computation cache. In build[59703](https://dev.azure.com/babylonjs/ContinousIntegration/_build/results?buildId=59703),startup cleanup reduced disk usage from 84% to 44%, but `Cache@2` laterrestored and attempted to archive a 19.5 GB Nx cache. The temporaryuncompressed tar exhausted the hosted agent's 72 GB OS disk.Nx 22 stores its cache database metadata outside `NX_CACHE_DIRECTORY`and keys it to the machine. Azure restored only the artifact directoryon each new hosted agent, so Nx reported the restored content asunrecognized and could neither use nor prune it. The configured 4 GBlimit therefore did not constrain the restored payload.## Change- Stop restoring and saving `NX_CACHE_DIRECTORY` through Azure`Cache@2`.- Retain npm and Playwright pipeline caches.- Retain the existing hosted-agent disk cleanup.- Retain Nx's bounded 4 GB local cache within each job.- Remove the obsolete Nx cache template parameters from the Build, ES6,and ES6Tools jobs.This removes both the unusable 19.5 GB restore and the duplicatepost-job tar write that caused the disk failure.## Validation- Parsed all changed Azure Pipeline YAML files successfully.- Verified no `Cache Nx computation`, `nxCacheKey`, or `nx: true`pipeline configuration remains.- `npm run format:check`- `npm run lint:check`- `npm run test:unit` — 5,658 passed, 1 expected failure, 64 skipped———Co-authored-by: Copilot App <223556219+[email protected]>———Co-authored-by: Copilot App <223556219+[email protected]>, GitHub
: 3D, Babylon.js, Framework, Game Engine, HTML5, JS, WebGL

Services

  • Fix bugs in your Wordpress Site $40.00 / hr
  • Bot Tok $45.00
  • Fix bugs in your PHP Symfony App $50.00 / hr
  • Tasks Automation using Node.js $50.00 / hr
  • REST API Development with Symfony $50.00 / hr

Blog

  • How to Pay with a Bank Card on Cryptomus
  • Complete Beginner’s Guide to Bot Tok: Terminal Commands Explained
  • Top Site to Gain Views on TikTok
  • Jfa Whatsapp Chatbot
  • TikTok Bot

Explore

  • Free 10 Tiktok Likes
  • Free 2K TikTok Views
  • Free 100 TikTok Favorites
  • Free 300 TikTok Shares
  • Buy TikTok Views
  • Free 100 Instagram Likes
Twitter
LinkedIn
YouTube
GitHub

© 2013-2026 Jordi Fernandes Alves (@jfadev)