Title: loading .fbx
Last modified: June 12, 2023

---

# loading .fbx

 *  Resolved [ahmadissa97](https://wordpress.org/support/users/ahmadissa97/)
 * (@ahmadissa97)
 * [2 years, 11 months ago](https://wordpress.org/support/topic/loading-fbx/)
 * Hello there,
   So im working on this react app that uses 3d objects (using R3F).
   So i loaded a 3d object (fbx) and the app worked fine, after building and deploying(
   offline locally, and online), the fbx directory would be non existent (asset 
   not loaded “404 – not found”). Whereas the app in VSCode works like a charm.Location
   of my model is in ‘~reactpress/apps/test-app/public/model.fbx’And code implementation:`//
   loads from public directlyconst fbx = useLoader(FBXLoader, './port.fbx');Any 
   idea as to why this is not functioning locally on wplocal or online?ps: i did
   add fbx MIME type ‘application/octet-stream’

Viewing 1 replies (of 1 total)

 *  Plugin Author [rockiger](https://wordpress.org/support/users/rockiger/)
 * (@rockiger)
 * [2 years, 10 months ago](https://wordpress.org/support/topic/loading-fbx/#post-16870400)
 * The build path is set in `package.json`. Maybe you need to adjust for that in
   production. Have a look in `package.json`.

Viewing 1 replies (of 1 total)

The topic ‘loading .fbx’ is closed to new replies.

 * ![](https://ps.w.org/reactpress/assets/icon-256x256.png?rev=2471443)
 * [ReactPress - Create React App for Wordpress](https://wordpress.org/plugins/reactpress/)
 * [Support Threads](https://wordpress.org/support/plugin/reactpress/)
 * [Active Topics](https://wordpress.org/support/plugin/reactpress/active/)
 * [Unresolved Topics](https://wordpress.org/support/plugin/reactpress/unresolved/)
 * [Reviews](https://wordpress.org/support/plugin/reactpress/reviews/)

## Tags

 * [fbx](https://wordpress.org/support/topic-tag/fbx/)

 * 1 reply
 * 2 participants
 * Last reply from: [rockiger](https://wordpress.org/support/users/rockiger/)
 * Last activity: [2 years, 10 months ago](https://wordpress.org/support/topic/loading-fbx/#post-16870400)
 * Status: resolved