Giter VIP home page Giter VIP logo

se-blender's People

Contributors

harag-on-steam avatar

Stargazers

 avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar

Watchers

 avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar  avatar

se-blender's Issues

LOD not showing up in game

I started adding Levels of details to my models. At first everything seams ok, xml includes information about LOD, mwm file with _LOD is generated but for some reason game is not using them. I tried everything that came to my mind, and can't figure out why is this happening. Did you have any problem with it? Or is there some step that I'm possibly missing?
Btw. thank you for this awesome add-on to Blender!

Blender 2.80 and higher

Doesn't appear to be compatible with 2.80, any chance of an update? The new 2.8 interface is sexy stuff ๐Ÿฅ‡

Support DX11 PBR texturing

Medieval Engineers and thus the VRage engine supports PBR textures. Allow to model that in Blender.

A possible way to do this might be to switch to Cycles and provide two node groups, one for DX9 textures and one for DX11 PBR textures. Take the image-paths from the input sockets of those groups.

InputError: no module named 'requests'

I get this error while trying to load your plugin in blender 2.77. If I drop the plugin in the plugins folder, itll give the same error when trying to select it from the list.

Trying to upload an image of the long error message. It references 3 python files and then ends with InputError: no module named 'requests'

I tried looking for a solution online, and this error seems to need another library in python that it doesnt come with for "requests", but adding that library then just makes blender immediately crash when the plugin is selected.

input error

The same thing happens in Blender 2.76. In 2.72, it just crashes.

Alternate texture sets for the individual source channels

According to Keen's texture converter tool SE uses this set of input channels:

  • albedo (RGB, sRGB) as defined by PBR
  • metal (single, sRGB) as defined by PBR
  • gloss, (single, linear) the inverse of roughness, also PBR
  • normal (RGB, linear) standard normal map
  • ao (single, sRGB) ambient occlusion
  • emissive (single, sRGB) emissive intensity, color is taken from albedo
  • dirt (single, sRGB) unknown use, defaults to full intensity
  • colormask (single, sRGB) masks recolorable parts of a texture
  • alphamask (single, linear) masks opaque parts of a texture, not all intensity levels are used in all situations. Decals do full blending but by default materials are either completely opaque > 0.5 or completely transparent < 0.5. For decals the other channel also get alpha-premultiplied by this channels, for default materials this doesn't happen.

The channels are packed into .dds textures (RGBA):

  • cm is [albedo, metal] (BC7, sRGB)
  • ng is [normal, gloss] (BC7, linear)
  • add is [ao, emissive, dirt, colormask] (BC7, sRGB)
  • alphamask (BC4, linear)

The Dx11 shader node the addon provides already has inputs for the original channels. Allow to switch the texture-slots of a material into a mode that has the individual channels as file slots instead of the combined final textures.

In this mode the addon expects the source images in a different format than .dds and derives final texture-filenames from those. A decision is needed how to handle situations like basename1_color, basename2_metal โ‡’ basename?_cm should be handled.

An added bonus would be to initiate the texture conversion directly from Blender instead of going through Keen's texture converter.

Addon is unmaintained

I'm a bit late to the party, but I am having an issue installing the addon to Blender. I downloaded the necessary version of Blender but still when I try to install the addon, simply nothing happens. No error code or processing, nothing. Then when I search for the addon name nothing shows up.

Report non-portable texture paths.

SE loads textures relative to a mod's base-path and additionally relative to <SE>\Content.

In principle that also works for absolute paths and paths that are no subpaths of the two base paths. But this is inherently non-portable because the mod author has no control over such paths on a client system. Because it will almost certainly cause texturing errors, when calculating texture paths report resulting paths that begin with <Letter>: (absolute) or .. (relative but no subpath) as errors.

Support Levels-of-Detail

A .mwm file can have a list of name-distance pairs that tells the game at which distance from the player to switch to another model. There is also a filter to tell the game if a level-of-detail should be rendered with the current graphic performance profile.

Provide UI for that. Probably a master-detail view similar to texture slots.
Export the list to the parameter.xml for MwmBuilder.

Custom SubtypeId fields not parsing {labels}

Here's just a simple little test:
I imagined that entering "${BlockPairName}_${CubeSize}" into the Large and Small custom SubtypeId fields should result in the same output as not having "use custom SubtypeIds" selected at all. But instead, the {label} fields are not parsed into their corresponding identifiers and instead remain as the strings "${BlockPairName}" which causes further problems down the line.

Image for clarification:
capture

Turn Dx9 textures into an extra option

As of 2016/03 the game only has a PBR renderer (commonly know as "Dx11"). The previous renderer ("Dx9") is no longer supported.

  • Hide the texture slots and additional options by default as they are confusing to newcomers
  • Provide an addon option to unhide them
  • Remove the corresponding documentation section

Support for new technique

Could you please add support for the 'Decal' technique for textures on export?
I'm not overly sure what the difference is between this and Alpha-Mask but I do know that using Alpha-Mask on Decal textures causes them to render very strangely in the holo preview when placing blocks.

Report missing UV-maps

MwmBuilder happily converts models that have objects without an UV-map. But Space Engineers cannot load such models. Report such models on export with an error.

Consider to also warn about meshes where some faces are not properly mapped (all UV-coordinates of the face's vertices are at (0.0, 0.0))

Support material export for duplicated objects

Currently objects will be missing materials on export if they partly consist of other duplicated objects and those objects are not selected by the export graph.

This would require to check the dupli settings of an exported object and then to recursively gather materials from the duplicated objects. The most straightforward to gather should be dupli-groups.

How does Blender's .fbx exporter handle this?

textureing channels

Hi, I currently dont own photoshop CS or CC, only elements 14. I'd like to know if I can texture with Paint.net somehow, If not is there a way to do it with elements or some other free product?

Space Engineers menu is not opening up

in the left-hand port under "Create" there is no Space engineers menu... I have tried re-launching blender, moving all the havok tools to the havok menu, and I know I hit the save button

Manually applying transformations for Havok objects is confusing

Havok expects mesh-objects that have all world-transformations already applied to them. Blender's Bullet physics-engine expects the opposite and will draw the green rigid-body wireframes at the wrong location when transforms are applied.

This is highly confusing to first-time users because if it looks right in Blender it will be wrong in Space Engineers and vice versa.

Possibly find a way to automatically apply transforms when running a Havok export-node.

Customizable folder layout

Currently the addon assumes the .blend file is located in the base folder of a SE mod. Models are placed in a folder Models/ with no option to organize them into further subfolders. Same for Textures\.

This is fine for most mods that only contain a few blocks but can get confusing for mods with a lot of blocks that all have large and small versions, construction models and LOD models.

Option to export large and small blocks with the same absolute size

Players often want to use a large block model with their small ship grids. This option would automate the export for that.

Necessary changes:

  • separate block dimensions for the small block version (ExportSettings, SESceneProperties, DATA_PT_spceng_scene)
    • reason: the model might occupy less than the full large block dimensions
    • requires an offset relative to the large block center that translates into a in the block-definition
    • drawing of the secondary small dimensions bounds
  • re-scaled mount point calculation for the small block-definition (mount_point_definitions() or its callers)
    • also needs to honor the offset
  • no model export for the small version, instead large block models are referenced in the block-definition (BlockExport, BlockDefinitionNode, MwmFileNode).

Automatic Blender Render texture slot 'Tex' of type 'None' interferes with the .mwm export

Under circumstances unknown Blender sometimes creates a Blender Render texture slot with a texture named "Tex" that is of type None. In order for materials to work in SE there needs to be at least one texture of type Image in a texture slot. But because there already is a texture the addon assumes the user knows what he's doing and doesn't create its dummy image texture. This results in MwmBuilder not finding any materials on the meshes and black textures in the game.

Implement an additional check to see if the existing texture slots have at least one texture of type Image to decide if the dummy texture is necessary or not.

Blender 2.79 breaks the export scale

Using blender 2.79 causes all models to export with a scale of x100 this can manually be fixed by either using 2.78c to export, or adjust the scale factor on the mwmbuilder object

Cannot read color and alpha from the same image-texture node

Currently the shader node-group that renders DirectX 11 textures produces some undesired rendering artifacts when both the color and alpha output of the same image-texture node are connected to it.

rendering artifacts

It seems Blender does not expect that several, unrelated image channels are contained in one image file and premultiplies the color output if the alpha output is used. That might be the cause for the rendering artifacts.

[1] forum-link with further details about the shader setup.

Recommend Projects

  • React photo React

    A declarative, efficient, and flexible JavaScript library for building user interfaces.

  • Vue.js photo Vue.js

    ๐Ÿ–– Vue.js is a progressive, incrementally-adoptable JavaScript framework for building UI on the web.

  • Typescript photo Typescript

    TypeScript is a superset of JavaScript that compiles to clean JavaScript output.

  • TensorFlow photo TensorFlow

    An Open Source Machine Learning Framework for Everyone

  • Django photo Django

    The Web framework for perfectionists with deadlines.

  • D3 photo D3

    Bring data to life with SVG, Canvas and HTML. ๐Ÿ“Š๐Ÿ“ˆ๐ŸŽ‰

Recommend Topics

  • javascript

    JavaScript (JS) is a lightweight interpreted programming language with first-class functions.

  • web

    Some thing interesting about web. New door for the world.

  • server

    A server is a program made to process requests and deliver data to clients.

  • Machine learning

    Machine learning is a way of modeling and interpreting data that allows a piece of software to respond intelligently.

  • Game

    Some thing interesting about game, make everyone happy.

Recommend Org

  • Facebook photo Facebook

    We are working to build community through open source technology. NB: members must have two-factor auth.

  • Microsoft photo Microsoft

    Open source projects and samples from Microsoft.

  • Google photo Google

    Google โค๏ธ Open Source for everyone.

  • D3 photo D3

    Data-Driven Documents codes.