spookyboo/hlmseditor

High Level Material Shader editor

hlmseditor's Issues

Some meshes cannot be painted on

It is not possible to paint on certain meshes, because there rendering to texture - which is used determine the uv coordinates - gives a strange result. See also http://www.ogre3d.org/forums/viewtopic.php?f=25&t=92368

Painting works, but sometimes not (inconsistent behaviour)

Painting works sometimes and sometimes not. The image is updated and saved in the /temp directory, but the blit functions doesn't work. Probably related with #10

Selecting texture sometimes results in wrong texture

When selecting a texture from the texture tree (to put as samplerblock on the node editor), the wrong texture is used. It happens in certain cases (no repro scenario available yet)

HLMSEditor tutorial or documentation

Sorry sir, is there a documentation or tutorial aboue this editor software? i don‘t understand the exactly function about this software

Warnings in Debug in combination with Cubemap and depth enabled

Cubemap json generates a lot of warnings in the log when depth is enabled (this is with all non-depth textures); the log message is only in Debug.

Painting again after saving a HLMS is not possible

Load a Pbs material, paint on the diffuse texture, save the material (updated texture is also saved). Then create a new paintlayer. Paint again on the texture layer. Painting is still done (see textures in the /temp directory). The TextureLayer::blitTexture however doesn't seem to work anymore (is it still the same datablock?).

Importing models often not possible

The import model plugin (AssImpPlugin) makes use of the assimp library. However, a lot of .d3s, .obj or .blend models cannot be imported, although the Ogre xml is created. Error in OgreMeshTool.log:

13:54:52: OGRE EXCEPTION(5:ItemIdentityException): Cannot locate an appropriate 2D texture coordinate set for all the vertex data in this mesh to create tangents from. in Mesh::suggestTangentVectorBuildParams at C:\Users\Henry\Documents\Visual Studio 2015\Projects\ogre2.1\OgreMain\src\OgreMesh.cpp (line 1850)

Grand+i10+Car.zip

Is this a bug in assimp or is Ogre too strict?

Resetting position and orientation requires two mouse clicks

Resetting position and orientation of the camera/mesh in the renderwindow requires two mouse clicks on the same marker button

Cannot load meshes with D3D11 render system

The following exception occurs when using the D3D11 render system (only in Release mode, not in Debug mode):
OGRE EXCEPTION(3:RenderingAPIException): Failure while waiting for a D3D11 Fence. Could be out of GPU memory. Update your video card drivers. If that doesn't help, contact the developers. in D3D11VaoManager::waitFor at C:\Users\Henry\Documents\Visual Studio 2015\Projects\ogre2.1\RenderSystems\Direct3D11\src\Vao\OgreD3D11VaoManager.cpp (line 1516)

Is this solved with commit 858c55c ?

Adapt to some recent changes with Ogre 2.1 Datablock

I'm going to PR on this probably, but a recent contribution in Ogre changed getFullName() into getNameStr() in datablock's classes, causing some breakage ;-)
https://bitbucket.org/sinbad/ogre/commits/1afa206e1a7ee031e04866a9343b84cdeb222eaf

Thumb is not reloaded

If thumb is missing and the noimage.png is displayed, the thumb is not refreshed when reloaded and added again to the material browser; only after a restart the thumb is refreshed (minor bug).

Up to date with the latest?

I'm building the editor using cmake on Ubuntu Linux 16.04.

I ran into a problem with Ogre including a header that is windows specific (despite Ogre itself building fine) and suppressed it by putting

add_definitions(-D_OgreAssert_H_)

in the Unix portion of the cmake file. I then got an error specifying that certain features in the code required the C++11 standard and that it had not been enabled. I fixed that by specifying the version of C++ by adding

set (CMAKE_CXX_STANDARD 11)

to the top of the cmake file. However, I then ran into a problem where a function call in the code appears to not be in sync with the Ogre library:

[ 65%] Building CXX object CMakeFiles/HLMSEditor.dir/framework/src/asset_propertywidget_texture.cpp.o CMakeFiles/HLMSEditor.dir/build.make:1022: recipe for target 'CMakeFiles/HLMSEditor.dir/source/src/hlms_utils_manager.cpp.o' failed make[2]: *** [CMakeFiles/HLMSEditor.dir/source/src/hlms_utils_manager.cpp.o] Error 1 make[2]: *** Waiting for unfinished jobs.... /home/charlesrwest/cpp/libraries/HLMSEditor/source/src/mainwindow.cpp: In member function ‘void MainWindow::saveDatablock(bool)’: /home/charlesrwest/cpp/libraries/HLMSEditor/source/src/mainwindow.cpp:1050:52: error: no matching function for call to ‘Ogre::HlmsManager::saveMaterial(Ogre::HlmsDatablock*&, Ogre::String&)’ hlmsManager->saveMaterial (datablock, fname); ^ In file included from /usr/local/include/OGRE/OgreHardwareBufferManager.h:39:0, from /usr/local/include/OGRE/OgreItem.h:37, from /home/charlesrwest/cpp/libraries/HLMSEditor/framework/header/ogre3_widget.h:32, from /home/charlesrwest/cpp/libraries/HLMSEditor/source/header/constants.h:29, from /home/charlesrwest/cpp/libraries/HLMSEditor/source/src/mainwindow.cpp:22: /usr/local/include/OGRE/OgreHlmsManager.h:303:14: note: candidate: void Ogre::HlmsManager::saveMaterial(const Ogre::HlmsDatablock*, const String&, Ogre::HlmsJsonListener*, const String&) void saveMaterial( const HlmsDatablock *datablock, const String &filena ^ /usr/local/include/OGRE/OgreHlmsManager.h:303:14: note: candidate expects 4 arguments, 2 provided

I have compiled and installed the latest of the v2-1 branch for both debug and release. If I may ask, what commit should I be using with the editor right now?

Thanks!

Crash when assigning pbs to Mesh

I was playing with your Editor to create some Materials.
i have downloaded the sources and used the binaries you provided.
when creating new pbs and assign it to a Mesh the tool crash.

Best version of Ogre to build this against?

Hello. I've tried to build this project but I can't find a version of Ogre to be compatible with this project.
It should be 2.1 but I get compiling errors. So maybe there are multiple revisions of ogre-next which call themselves 2.1.
It would be helpful to know the commit revision which would suit this project.