We use cookies to ensure that we give you the best experience on our website. If you continue to use this site we will assume that you are happy with it.

Publishing on other server (webhosting)

Home Forums General Questions Publishing on other server (webhosting)

Viewing 15 posts - 1 through 15 (of 20 total)
  • Author
    Posts
  • #5903
    RMandik
    Customer

    Dears

    before I buy verge I want to test everything….

    can you help please how to make the structure of all the files for publishing on external servers? I am absolute amateur as for the web programing.

    I mean exact file content html, css…
    what to do with file gltf, bin etc….
    I placed all the files but I stopped in this phase… just loading 30%…and stopped..
    http://www.pracovni-stoly-sse.cz/

    #5904

    Hi,

    I checked your link with the browser console open – it seems that for some reason it cannot load the main .gltf file called “01 SSE.gltf” – which I believe is due to the space character in the file name that your web server cannot handle.

    I’d suggest trying to re-create your project without a space in its name (mere renaming won’t work).

    can you help please how to make the structure of all the files for publishing on external servers?

    The entire app folder should be uploaded. Make sure all the used textures are located inside that folder. You can skip the .max or .blend files and the visual_logic.xml file as they are not needed for work of a deployed app.

    Chief 3D Verger | LinkedIn | Twitter

    #5905
    RMandik
    Customer

    thx, but did not help, still freeze at 30% loading
    :-(

    #5907
    RMandik
    Customer

    I replaced my project with PBR project (monkey helmet)
    freeze at 30% still alive :-(
    here enclosed the list of the uploaded files

    #5909

    I checked again in the console – I guess your IIS web server requires adding the .xz file extension to its mime map.
    https://docs.microsoft.com/en-us/iis/configuration/system.webserver/staticcontent/mimemap

    As a possible workaround, you can upload your app to Verge3D CDN and embed them to your website using iframe.

    Attachments:
    You must be logged in to view attached files.

    Chief 3D Verger | LinkedIn | Twitter

    #5911
    RMandik
    Customer

    dear
    i tried to load my project on your network Verge3D … after several attempts succesfully. fine

    but it is so so so long time opening that aplication .. i am afraid nobody will wait :-(
    is there anything wrong with my project?

    https://cdn.soft8soft.com/AROAJSY2GOEHMOFUVPIOE:1252550e6d/applications/01SSE/index.html

    #5916
    jem
    Customer

    Hello RMandik,
    Can you simplify your geometry? Your .bin file is 70MB. In my experience, that is too large. Your scene is fairly simple. You should be able to reduce the complexity of the mesh dramatically without any noticeable effects. Here are some actions that I would do, if it were my project.
    1. Eliminate small features. Your socket head cap screws have chamfers. No one will see these tiny features and they add a lot of weight to the model.
    2. Eliminate hidden surfaces. Your square tubing has inside walls. No one will see those inner walls but that data is in your .bin.
    3. Eliminate as many holes and bevels and rounds as you can. These round features dive up the face count. I think that your injection molded plastic parts have hidden tiny rounds and spheres on the inside.
    4. Use smooth shading and use less vertices. The cylinder shaped objects in your scene all seem to have 32 sides. You can model that same geometry in blender in a more efficient way. Create cylinders with fewer faces (the Blender tool calls them vertices). You can use low-poly meshes with smooth shading and object will still look nice.
    5. If your scene data originated in CAD, do all of the steps listed above in CAD before exporting to Blender. It will be easier.
    Good luck, :good:
    Jem

    Jeremy Wernick

    #5921

    I can only add to the above that you can enable loading of a compressed version of your scene as described here https://www.soft8soft.com/docs/#manual/introduction/Asset-compression


    @Jem
    , thanks for the advice and detailed explanations!

    Chief 3D Verger | LinkedIn | Twitter

    #6210
    loom
    Customer

    Hi,
    i run into troubles with edge. i got Error 401 access denied on all textures. I suspect the error occures on the server side of my webhoster.

    Do i have to concern about privacy if i publish it the verge3d Server ?
    How to remove them after testing ?

    #6211

    Hi,

    i run into troubles with edge.

    You mean Microsoft Edge browser?

    i got Error 401 access denied on all textures.

    Can you check if relative file paths are used?

    Do i have to concern about privacy if i publish it the verge3d Server ?

    A published app will only be seen to persons with whom you share the app link.

    How to remove them after testing ?

    There is a link in the App Manager to access and remove files on the Network Directory.

    Attachments:
    You must be logged in to view attached files.

    Chief 3D Verger | LinkedIn | Twitter

    #7350
    tcdoe
    Customer

    This I need to work on as well. Placeholder.

    CEO, ABĒMIS LLC
    visit: abemis.com

    #11878
    ziwei
    Participant

    Hello, I am in the same situation as you. How did you solve it? Thank you!

    #11879

    Hi,

    I am in the same situation as you.

    Can you please elaborate?

    Chief 3D Verger | LinkedIn | Twitter

    #11922
    ziwei
    Participant

    Hello, there’s no problem with app mannger, but only 30% can be loaded into the local server. The same is true for other servers in the LAN. It’s easy to make. It’s a water molecule stick model.I think it’s lack of what driver to load. The browser is chrome.

    #11935

    Hi,

    you’re serving from localhost without the port number – must be localhost:8668

    Chief 3D Verger | LinkedIn | Twitter

Viewing 15 posts - 1 through 15 (of 20 total)
  • You must be logged in to reply to this topic.