Jump to content
The Dark Mod Forums

Renderbump


Springheel

Recommended Posts

Has anyone here used renderbump as part of their workflow? I'm just starting to try and use it, and tutorials are difficult to find. As far as I can tell I'm doing everything right, but when I try it, the console pops up a few errors I don't have time to read (I caught something about can't find image) and then the screen goes grey with weird pixels. Doom does create the normalmap file, but the contents are solid grey.

Link to comment
Share on other sites

I had been using renderbump before I learnt how to do it in Max (it gives some better control). I remember that it took me some time to figure out what was wrong. Are you working with LWO or ASE files?

Few questions:

- does your low poly model have UV applied?

- do LP and HP occupy the same space? (they should overlap each other in 3D app before exporting)

- are paths correct? where did you place your models? Separate folder is a good idea (f.e.models/renderbump or whatever).

- does low poly model points to existing material shader?

- what are your renderbump parameters? (those in material declaration)

Link to comment
Share on other sites

I remember that it took me some time to figure out what was wrong. Are you working with LWO or ASE files?

 

I'm working with .lwo files.

 

- does your low poly model have UV applied?

 

Yes.

 

- do LP and HP occupy the same space? (they should overlap each other in 3D app before exporting)

 

Ah, no, I don't think they do. So their origins have to be in the same place but they are separate files, or do you mean they have to be on separate layers in the same file?

Link to comment
Share on other sites

Ah, no, I don't think they do. So their origins have to be in the same place but they are separate files, or do you mean they have to be on separate layers in the same file?

origins the same, one overlapping the other, but exported in separate files.

That might be the cause - grey (=blank) normal map means that rays did not reach hipoly model (it was too far from hipoly).

Link to comment
Share on other sites

@Springheel: I wrote a renderbump tutorial on the wiki a while back, but I don't know if it contains any more information than you already know. I only used it once - then angua tried xNormals and found it to work much better. Sometimes the resulting normalmap has to be tweaked after xNormals is done with it, but overall it's very fast.

Link to comment
Share on other sites

@Pink: That was it, thanks. It seems to have worked now.

 

@greebo: I did read that one but I didn't understand some of the non-lightwave terms. I assume xNormal is for blender?

Link to comment
Share on other sites

I got it to work more or less, but there are some weird shapes overlapping the normals. Any idea what those greenish triangles are? Should I leave the points unwelded when running this? That's what it looks like to me, vaguely, like something is merged.

 

feastplate_local.jpg

Link to comment
Share on other sites

Those weird shapes are most likely polys that overlap somewhere. Best to have NO overlapping polys anywhere on model. Makes it hard to reuse tex and save space.

 

I've been using renderbumpflat and I like it alot better. Reasons:

1-you don't have to use material shader, just uv map the obj.

2-Easy to avoid weird shapes/overlapping polys

3-no need to have high and low poly models overlapped/exported, only need high poly.

 

I basically lay out the high poly object flat, or just small pieces of it. I did this with my metal chest. I can have several flat images, render them, then paste together in photoshop. Then uv map the low poly object and adjust uv's to fit.

Dark is the sway that mows like a harvest

Link to comment
Share on other sites

@greebo: I did read that one but I didn't understand some of the non-lightwave terms. I assume xNormal is for blender?

No, xNormals is a stand-alone application, which can handle at least ASE (I haven't checked LWO, I have to admit). Yes, some terms are Blender-specific, but you can skip the parts "Apply Scale and Rotation" and "Export your Mesh" - just export your model to LWO. Anyway, if renderbump is working fine for you, there's no need to switch.

 

Also, I don't know if ASE and LWO are working equally well with renderbump, but I always got strange results with my ASEs and had to play around with the trace a bit. And it takes ages. xNormals takes just a few seconds and is supporting multi-core processors.

Link to comment
Share on other sites

I found out that the problem had to do with some points that had two sets of uv coordinates. I'll have to check out xNormals though, as renderbump takes forever.

Link to comment
Share on other sites

I found out that the problem had to do with some points that had two sets of uv coordinates.

 

If you mean parts of the UV map were non-unique (i.e. mapped to more than one place on the model) then yes, that would cause problems.

Link to comment
Share on other sites

I found out that the problem had to do with some points that had two sets of uv coordinates.

You can't have overlapping polygons only at the moment of baking normal maps. So when you want to have your model with overlapping polygons on texture, just save that UV coordinates set, then take all overlapping polygons out of the UV space (out of 0,0 to 1,1 range), so no polygons are overlapping. Export that model and use it for renderbump. When you're happy with the result you can load the previous UV set.

 

I use Max, so I can't tell you where are Save UV and Load UV commands but I'm pretty sure Lightwave can do that as well.

 

BTW: not everything looks fine after renderbump. For instance that strip at the bottom of your baked texture. It could be corrected in 3D application, which gives you control over the projecting rays direction (again, I don't know how to do that in Lightwave). Or you can do it also in Photoshop (Gimp) - just make a simple height map simulating those round edges and run nVIdia filter.

Link to comment
Share on other sites

Something still doesn't look right.

 

Here is the model in-game (it's the covered serving dish).

On the left is the model with both the renderbumped normalmap and the metal normalmap 'addnormaled' together. On the right is JUST the metal normalmap.

 

servingdish1.jpg

 

I almost think it looks better on the right, but specifically I'd like to know why part of the handle is black when the normalmap is applied?

 

normal1.jpg

 

Here's the current version of the renderbumped normalmap with the handle part circled in red. It looks fine to me. The same part of the model was black the last time, before I totally redid the uvmap.

 

Any ideas?

Link to comment
Share on other sites

Spring - could you post an image of UV layout? and image of low and hipoly models overlapping each other (with mesh visible)? Maybe this could tell us more...

Link to comment
Share on other sites

Yeah, that's what I though as well. Looks like distance from low to high poly model is bigger at that spot than at other places and maybe rays miss high poly model (they never go too far to speed up projecting process). And you can see there's a mess on the normal map for the corresponding polygons.

Just try to fit low poly mesh as much as you can to high poly mesh. And if you want to keep that shape of handle, you can revert it later, after baking the normals.

Link to comment
Share on other sites

Join the conversation

You can post now and register later. If you have an account, sign in now to post with your account.

Guest
Reply to this topic...

×   Pasted as rich text.   Paste as plain text instead

  Only 75 emoji are allowed.

×   Your link has been automatically embedded.   Display as a link instead

×   Your previous content has been restored.   Clear editor

×   You cannot paste images directly. Upload or insert images from URL.

  • Recent Status Updates

    • datiswous

      I tried to upscale the TDM logo video. First try:

      briefing_video.mp4 You can test it ingame by making a copy of the core tdm_gui.mtr and place it in your-tdm-root/materials/ , then edit line 249 of that file into the location where you placed the new briefing.mp4 file.
      What I did was I extracted all the image files, then used Upscayl to upscale the images using General photo (Real-Esrgan) upscale setting and then turn it back into a video.
      I might have to crop it a bit, the logo looks smaller on screen (or maybe it's actually better this way?). My video editor turned it into a 16:9 video, which I think overal looks better than 1:1 video of original.
      · 1 reply
    • nbohr1more

      Trying to be productive on my down-time before Capcom releases Akuma and my son is constantly on my PC playing Street Fighter...
      · 1 reply
    • OrbWeaver

      Finally got round to publishing a tutorial on baking normal maps in Blender, since most of the ones we have are inaccessible or years out of date.
      · 2 replies
    • nbohr1more

      The FAQ wiki is almost a proper FAQ now. Probably need to spin-off a bunch of the "remedies" for playing older TDM versions into their own article.
      · 1 reply
    • nbohr1more

      Was checking out old translation packs and decided to fire up TDM 1.07. Rightful Property with sub-20 FPS areas yay! ( same areas run at 180FPS with cranked eye candy on 2.12 )
      · 4 replies
×
×
  • Create New...