OGRECave/ogre

Welcome to the Ogre3D channel - www.ogre3d.org

crjc

@crjc

With the latest version i get:

CMake Error:
  Running

   '.../vcpkg/downloads/tools/ninja-1.10.1-osx/ninja' '-C' '.../vcpkg/buildtrees/ogre-next/x64-osx-mixed-dbg' '-t' 'cleandead'

  failed with:

   ninja: error: build.ninja:788: multiple rules generate lib/macosx/OgreMainStatic.framework/Versions/2.2.4/Headers/OgreTagPoint.h [-w dupbuild=err]

SNiLD

@SNiLD

Yeah and if you run that version with -w dupbuild=warn you probably get them as warnings again

But sure, that's something Ogre devs should fix (these are not issues that make the build fail though)

crjc

@crjc

Yeah I've tried to get Vcpkg to pass that to ninja but had no success. Was just curious if it would be a simple fix to get rid of those duplicate rules

Pavel Rojtberg

@paroj

Would you recommend using Ogre 1 instead for new projects?

I would say it depends what your project is. See https://www.ogre3d.org/about/what-version-to-choose ogre1 still has the ecosystem advantage - like being available in the msys2 repo

crjc

@crjc

auto ogreRoot = OGRE_NEW Ogre::Root( "", "", "ogre.log", "Test");

auto renderers = ogreRoot->getAvailableRenderers();

With this minimal amount of code, is it expected for renderers to be empty?

SNiLD

@SNiLD

Yeah, you need to load the renderers, because they're plugins

So ogreRoot->loadPlugin("RenderSystem_GL3Plus"); before getting renderers

crjc

@crjc

Ah, thank you!

crjc

@crjc

Upon creating a basicWorkspaceDef, I'm triggering an assertion

compositorManager->createBasicWorkspaceDef( workspaceName, backgroundColour, Ogre::IdString() );

Assertion failed: (!(mHash == idString.mHash && strcmp( mDebugString, idString.mDebugString ) != 0) && "Collision detected!"), function operator<, file /OgreMain/include/OgreIdString.h, line 231.

Is it possible there's another simple thing I've missed?

crjc

@crjc

This only happens when I use "addWorkspace", not sure if this is a bug - I've added more details here: OGRECave/ogre-next#147

Claire Jervert

@CJervert_twitter

I having trouble converting FBX models to Ogre3D skel and mesh xml files. Any suggestions.

Pavel Rojtberg

@paroj

stop having trouble and just do it!

Guillermo Ojea Quintana

@sercero

How are you doing it? Through Blender?

Might be a scaling issue

Claire Jervert

@CJervert_twitter

I am working with an AI engineer who used that engine to animate a robot. I gave him a FBX file to animate in Maya and it doesnt seem to work for him. Guillermo please tell me more about scaling you mentioned.

Im trying to use the same settings on the animation of the 3D character as the robot has on its servo motors.

Guillermo Ojea Quintana

@sercero

I use Blender to export the models for OGRE3D. In my case when importing FBX from the Mixamo models and then exporting I had trouble with the model (which is scaled to 0.01x)

I don't know how you are exporting the model to OGRE

Are you using Maya?

Claire Jervert

@CJervert_twitter

Yes i am using Maya

Guillermo Ojea Quintana

@sercero

I am not familiar with Maya or its exporter.

If you can share the model I might take a look at it importing it in Blender and seeing if it exports better through that software. Or you could try it yourself.

Claire Jervert

@CJervert_twitter

Ill try. What file extension should i use to export to Orge 3D and what scale should it be.

Guillermo Ojea Quintana

@sercero

The exporter should set the extension automatically. There should be a .mesh for every mesh a .skeleton for every armature

The scale depends on what consistent scale you are using in Maya and in the game. In my case every Blender unit is a meter and that is the same in the game

I know that the Blender default cube is 2 meters across so I use that as a reference

http://wiki.ogre3d.org/Maya+Exporter

Claire Jervert

@CJervert_twitter

I imported the fbx into Blender and the rig seem quite messed up with the rig joints outside of the face.

Pavel Rojtberg

@paroj

you could try to import the fbx directly using the assimp plugin: https://www.ogre3d.org/2020/09/20/ogre-1-12-9-released

Guillermo Ojea Quintana

@sercero

@paroj suggestion is good. I purchased the Better FBX plugin for Blender because the default is not very good.

Claire Jervert

@CJervert_twitter

Gillermo, this is a little over my head. Can i send you the model via WeTransfer. For your eyes only.

Guillermo Ojea Quintana

@sercero

Claire Jervert

@CJervert_twitter

Whats your email?

Guillermo Ojea Quintana

@sercero

ghojea@gmail.com

Adrian Edwards

@MoralCode

does anyone know of a guide or rough outline for how to take a DirectX C# project and translate it to OGRE so that the project can be made cross-platform?

Claire Jervert

@CJervert_twitter

Guillermo. About 20 minutes

Claire Jervert

@CJervert_twitter

Resent new files the previous ones were earlier versions of the files. Thanks.

Guillermo Ojea Quintana

@sercero

@MoralCode OGRE3D hast C# bindings and also there is MOGRE (but I think it is outdated). You will have to convert your code to use the OGRE API which abstracts you from the DirectX API and you will have to also do something about your shaders. One option is to use CG which is not being supported since 2012, another option is porting your shaders to GLSL and another option (more recent) is using the newfangled OGRE unified shader (the language is similar to GLSL).

@MoralCode I think it is better that you ask this in the forums to get better help. You can start here: https://ogrecave.github.io/ogre/api/latest/tutorials.html

crjc

@crjc

I tried doing

sceneManager->setFog(Ogre::FOG_LINEAR);

In Ogre 2.3, however it doesn't seem to have done anything, is there something that I might of missed?

Guillermo Ojea Quintana

@sercero

See if this helps: https://forums.ogre3d.org/viewtopic.php?t=82878

crjc

@crjc

Ah thanks, so setFog isn't supposed to actually do anything?

Guillermo Ojea Quintana

@sercero

I know that in OGRE 1.x setFog only works if your materials use the Fixed Function Pipeline. That's why I assumed that in OGRE 2.x the function wouldn't even exist

But I think that it is possible to pass a fog parameter to your shaders in OGRE 1.x. It seems that in 2.x as well

Neonit

@Neonit

Can somebody explain to me, why the tutorial code in Samples/2.0/Tutorials/Tutorial01... (also 02 and 03) only defines MainEntryPoints::createSystems() on Apple and IOS? This leads to a linker error on Windows, because the method never gets defined elsewhere. Or did I miss something?

(Also, at least in Tutorial01, MainEntryPoints::getWindowTitle() is also missing on all platforms)

crjc

@crjc

_getDerivedScale is returning +inf values when I'm loading a skeleton with the Ogre_glTF plugin. Does anyone know a work around: Ybalrid/Ogre_glTF#32 ?

Matías N. Goldberg

@matiasgoldberg_twitter

Can somebody explain to me, why the tutorial code in Samples/2.0/Tutorials/Tutorial01... (also 02 and 03) only defines MainEntryPoints::createSystems() on Apple and IOS? This leads to a linker error on Windows, because the method never gets defined elsewhere. Or did I miss something?

Hi @Neonit ! Sorry for late reply

Tutorial01 never calls MainEntryPoints::mainAppSingleThreaded nor MainEntryPoints::mainAppMultiThreaded as it defines its own custom main loop for tutorial purposes.

(i.e. INT WINAPI WinMainApp does what mainAppSingleThreaded would do). It does on iOS because iOS was adding too much complexity for a tutorial.

It shouldn't give you linker errors; but I think I see how it may be possible. What compiler were you using? And was it Debug or Release? x64 or x86?
Cheers

Neonit

@Neonit

@matiasgoldberg_twitter MSYS2 gcc, I think it's RelWithDebInfo (so basically Release) and x64.

Where communities thrive

People

Repo info

Activity