[email protected]
Twitter
LinkedIn
Youtube
GitHub
  • Services
  • Blog
  • Dépôts
  • GitHub
  • CV
    • LinkedIn
    • PDF
  • Contact
Produit a été ajouté à votre panier

Chariot

Cours de Babylon.js

Mai 1, 2015Outilsjfadev

Babylon.js est un framework complet pour créer des jeux 3D à l'aide de HTML5 et WebGL basé 100% en JavaScript, développé par des programmeurs de Microsoft. Il fonctionne correctement sur Firefox et Chrome et il est compatible avec les caractéristiques suivantes:

  • Graphiques complets de scènes , luz, cámaras, materiales y texturas
  • Moteur de collisions
  • Sélection de scènes
  • Antialiasing
  • Moteur d'animations
  • Systèmes de particules
  • Sprites et layers 2D
  • Moteurs d'optimisation
  • Matériaux standard au niveau du pixel
  • Brouillard
  • Blending alpha
  • Tests alpha
  • Billboarding
  • Mode plein écran
  • Maps d'ombres et maps de variation d'ombres
  • Rendu de textures
  • Textures dynamiques (canvas)
  • Textures vidéo
  • Caméras (perspectives et orthogonalité)
  • Clonage de maille
  • Maillages dynamiques
  • Maps de hauteur
  • Les scènes de Babylone peuvent se convertir en. OBJ, .FBX, .MXB
  • Exporte vers Blender

 

Ci-dessous est un cours vidéo bien très bien expliqué en espagnolOscar Uh Pérez (Develoteca) qui nous donne toutes les compétences nécessaires pour mettre les mains dans la pâte.

 

 

Aussi, je laisse quelques tutoriaux intéressants de Julian Chenard pour commencer avec Balylon.js dans le lien suivant: http://www.pixelcodr.com/

 

Plus de tutoriels: http://www.babylonjs-playground.com/

 

Dépôt

Babylon.js est un puissant, belle, simple, et jeu ouvert et moteur de rendu emballé dans un framework JavaScript convivial.
https://github.com/BabylonJS/Babylon.js
3,666 fourches.
25,820 étoiles.
27 questions ouvertes.

commits récents:
  • [interface graphique] Fix Line.connectedControl with adaptive scaling (#18703)> 🤖 *This PR was created by the create-pr skill.*Fixes `GUI.Line.connectedControl` when a fullscreen`AdvancedDynamicTexture` adapts to the engine hardware scaling level.Forum report: https://forum.babylonjs.com/t/63804 Deterministic repro: https://playground.babylonjs.com/#NX7KQL#0The connected control center is expressed in global GUI layoutcoordinates, while the line endpoint is drawn relative to the lineparent. Adaptive scaling gives the root container a nonzero layoutorigin, causing that origin to be applied twice. The fix converts theconnected center to parent-local coordinates and makes the currentparent measurement available before the line's first measurement pass.Adds regression coverage for both coordinate conversion and first-layoutbehavior.———Co-écrit par: Copilot Autofix powered by AI <175728472+[email protected]>, GitHub
  • réparer(inspector-v2): don't flood scene explorer with per-frame active camera notifications (#18700)### IssueWith Inspector V2 open, any scene where `scene.activeCamera` istransiently reassigned during rendering — e.g. a `RenderTargetTexture`with its own `activeCamera` and `REFRESHRATE_RENDER_ONEVERYFRAME` —floods the browser console with periodic React warnings:“`Maximum update depth exceeded. This can happen when a component calls setState inside useEffect…“`### CauseThe scene explorer's camera entity command ("Activate and AttachControls") notifies its `onChange` observable unconditionally on every`scene.onActiveCameraChanged`. Render target rendering swaps`scene.activeCamera` to the RTT camera and back each frame, so theobservable fires (at least) twice per frame, and each notificationsetStates in the scene explorer's aside `useEffect` — a per-frame Reactupdate loop even though nothing user-visible changed.### FixDefer the active-state check to a microtask so synchronous mid-frameswaps have settled by the time it runs, and only notify when thecamera's effective active state (`getActiveCamera() === camera`)actually changed. Transient RTT swaps settle back to the same camerawithin the same task, so they no longer produce any notifications;genuine camera activations still notify (now at most once per change).The frame graph activation path now goes through the same guarded notifyso the cached state can't go stale.🤖 Generated with [Claude Code](https://claude.com/claude-code), GitHub
  • Fix physics plugin not releasing empty Havok world regions (#18699)Hey there,I noticed that havok world region count tends to grow quite a lot, andfound some gaps in region removal.So this PR adds a dedicated helper to accumulate and flush regions to beremoved.Let me know what you think!Clause de non-responsabilité: the patch was written by Codex, but I reviewed it myself., GitHub
  • exploit(flowGraph): edit live scenes from the Flow Graph Editor + Inspector (#18695)## MotivationThe Flow Graph Editor requires a working scene for context, but today itonly operates on a Playground/snippet scene it mints itself. That makesit impractical to inspect or tweak a flow graph that belongs to a real,running application. This PR connects a **live host `Scene`** to theeditor and surfaces flow graphs in **inspector-v2** so developers canopen and edit the graphs their app is actually running.## What's included### Core (`packages/dev/core/src/FlowGraph`)- `FlowGraph.edit(configurer?)` + static `FlowGraph.EditorURL`, mirroringthe proven `nodeGeometry.ts` launch pattern, so a developer can do`myFlowGraph.edit()` to open the editor bound to their own graph/scene.- `FlowGraphCoordinator.OnFlowGraphAddedObservable` /`OnFlowGraphRemovedObservable` so the inspector's flow-graph list canlive-refresh as graphs are created/removed/disposed. Covered by new unittests (8/8 pass).### Editor — attach to a host scene (`packages/tools/flowGraphEditor`)- `SceneContext` gains a readonly `ownsScene` flag. When the editor islaunched with a `hostScene`, the preview pane **attaches to that scene**instead of creating its own Engine+Scene, and never disposes theborrowed scene.- `sceneSource` union widened with `"host"`; host mode shows aninformational banner instead of a 3D viewport (a foreign scene bound tothe app's own engine/canvas cannot be re-rendered on the editor'sengine).### Inspector-v2 (`packages/dev/inspector-v2`)- New **"Flow Graphs"** scene-explorer section listing every graphacross the scene's coordinators, with an **"Edit Graph"** command.- New properties section (predicate: `instanceof FlowGraph`) with an"Edit Graph" button.- Both open the editor bound to the live scene via `flowGraph.edit({flowGraphEditorConfig: { hostScene: flowGraph.scene } })`.## Host-safety fixes (from a second review pass)The editor was designed around owning its scene/engine, so a few pathswould have mutated the live application when pointed at a host graph.All are now guarded:1. **Engine timing** — `_applyEngineTimeScale` patches`engine.getDeltaTime` / `customAnimationFrameRequester` with no restorepath. It now early-returns in host mode, so the Speed control can neverbreak the live app's render loop.2. **Stopping the live graph** — `set flowGraph` no longer calls`flowGraph.stop()` on a host graph (either the incoming graph or aswapped-out one), so opening/closing the editor doesn't halt a runningapplication's graph. `hostScene` is now assigned before thecoordinator/graph load path runs so the guard sees it.3. **`createContext` wrapper leak** — the editor wraps the graph's`createContext`; it's now restored on editor teardown(`restoreLiveGraph()`), so the wrapper never outlives the editor andre-injects editor snapshot data into contexts the app creates later.## Known caveats- **Host preview is an info banner, not a live 3D viewport** — a scenebound to the app's engine/canvas can't be re-rendered on the editor'sown engine.- **Editing a live graph is the user's call** — the editor no longerstops it, but authoring on a running graph is inherently live.- **`Edit` lazy-loads the editor UMD** from `FlowGraph.EditorURL` (CDN),so it needs network at runtime — same model as the node editors.## Validation- `flowGraphEditor` + dev packages typecheck clean.- ESLint + Prettier clean on all changed files.- 8/8 `flowGraphCoordinator` unit tests pass (3 new for theobservables).- Tree-shaking manifest regeneration (precommit) produced **no netdiff** — the core additions mirror `nodeGeometry.ts` and don't perturbside-effect classification.Co-authored-by: Copilot App <223556219+[email protected]>———Co-écrit par: Copilot App <223556219+[email protected]>, GitHub
  • Mise à jour de version 9.17.0, Plateforme Babylon.js
: 3D, Babylon.js, Framework, Game Engine, HTML5, JS, WebGL

Services

  • Excel2chatGPT $10.00
  • Bot Tok $45.00 $30.00
  • Correction de bogues dans votre application PHP Symfony $70.00 / heure
  • Correction de bogues de votre site Wordpress $70.00 / heure
  • Automatisation des tâches à l'aide de Node.js $70.00 / heure

Blog

  • Comment payer avec une carte bancaire sur Cryptomus
  • Guide complet du débutant sur le tok bot: Commandes de terminal expliquées
  • Meilleur site pour gagner des vues sur TikTok
  • Chatbot Jfa Whatsapp
  • Bot pour TikTok

Explorer

  • Gratuit 10 J’aime Tiktok
  • Vues TikTok 2K gratuites
  • Gratuit 100 Favoris TikTok
  • Gratuit 300 Partages TikTok
  • Acheter des vues TikTok
  • Gratuit 100 J'aime Instagram
Twitter
LinkedIn
Youtube
GitHub

© 2013-2026 Jordi Fernandes Alves (@jfadev)