Print

Please login or register.
1 Hour 1 Day 1 Week 1 Month Forever
Login with username, password and session length

[LordZorintrhox]

- There is code to ensure that buildings are oriented in sensible ways (chairs face tables for instance), and for this to work the models should face towards -y.

Unless he hasn't dealt with statue orientation, though that is a pretty simple algorithm: orient the statue facing away from the nearest wall and towards the nearest cliff within a given distance threshold.  Otherwise, default to facing North.  Not perfect but it will work most of the time.

[Andir]

- There is code to ensure that buildings are oriented in sensible ways (chairs face tables for instance), and for this to work the models should face towards -y.

Unless he hasn't dealt with statue orientation, though that is a pretty simple algorithm: orient the statue facing away from the nearest wall and towards the nearest cliff within a given distance threshold.  Otherwise, default to facing North.  Not perfect but it will work most of the time.

I tend to like placing statues along the bridge leading to my main entrance... no walls.

[Shima]

New bug: "Ignore Snow" causes a crash during load on tundra maps (And probably any other snowy place).

[Baboonanza]

New bug: "Ignore Snow" causes a crash during load on tundra maps (And probably any other snowy place).

Oops.

Unless he hasn't dealt with statue orientation, though that is a pretty simple algorithm: orient the statue facing away from the nearest wall and towards the nearest cliff within a given distance threshold.  Otherwise, default to facing North.  Not perfect but it will work most of the time.

It all uses the same code, with the exception of chairs/tables, and more-or-less works as you describe. The algorithm will start off simple so please don't expect it to be perfect, I'll gradually enhance it as I go and more examples appear.

The same applies to the model materials. All materials are represented by a colour blended with a texture at the moment. The blending is based on the alpha value of the texture though, so you can have opaque areas if desired. I'll be improving this by adding an additon material texture stage and possible bump maps in the fucture (the issue here is one of asset creation rather than technical, bump maps).

[Shima]

Gentlemen, I give you, the great flagpole of Blazerazor.

Spoiler (click to show/hide)

I should note it's giving me a non-fatal texture error, something about being unable to find the smoothed wall texture.  It strikes all slashes and underscores, looks like some error in the database.  This started after I dug up and later smoothed the microcline and orthoclase, so it's probably related to them.

[smjjames]

Also, for some reason the dump from DF acts a bit glitchy sometimes with the Mayday set.

Sometimes when I try to dump the map to the application, it gives me the suppourted version not found error, but when I move around a bit or something, it goes through. I have no idea why it does this because it does load the map, but moving around a bit or unpausing/pausing gets it to work after a bit of fiddling around.

Sorry for repeating myself, but not sure if you caught what I said earlier ^^^ .

I can't seem to find or see a connection as to what is causing this problem, other than moving around in the game seems to help. But, it really shouldn't matter where your current window is ingame, right? Unpausing and pausing also seems to help.

Also, I think having the game unpaused when I try to dump also gives a similar error, probably understandable since it can't track real time changes.

[Idles]

Neato ice fortress.

[LordZorintrhox]

So I figured I should post a pic of the end product for review before I upload it.  This would be the texture intended for metals, but both it and the stone one obviously need some tweaking in Photoshop to mesh with the color blending properly.  The model is shown with no lighting, just the texture.

Spoiler (click to show/hide)

686 triangles.  If you support LODs, then I can get two more reductions, possibly a third.

Opinions?  Suggestions?

[Greiger]

That is a very nice dwarf statue. Very nice.  Do you do 3D modeling professionally or something? 

[Baboonanza]

Also, for some reason the dump from DF acts a bit glitchy sometimes with the Mayday set.

Sometimes when I try to dump the map to the application, it gives me the suppourted version not found error, but when I move around a bit or something, it goes through. I have no idea why it does this because it does load the map, but moving around a bit or unpausing/pausing gets it to work after a bit of fiddling around.

I didn't reply as I couldn't think of anything useful to say, I can't think of anything that would cause this error. If I get time before the next release I'll add some fallback code and I'll test it with the Mayday set (not that it should make any difference). Are you running on a multi-core system? Are the apps both running on the same core?

So I figured I should post a pic of the end product for review before I upload it.  This would be the texture intended for metals, but both it and the stone one obviously need some tweaking in Photoshop to mesh with the color blending properly.  The model is shown with no lighting, just the texture.

Spoiler (click to show/hide)

686 triangles.  If you support LODs, then I can get two more reductions, possibly a third.

Opinions?  Suggestions?

I second that, very nice! I can already support multiple LODs if I decide to use them, so having them would be great.

Also, there isn't a limit on the number of statues you can have. If there is more than one statue specified it will randomly choose between them so there is some variety. This applies to other furniture too.

[Andir]

Could you key the model off of the material (or can you grab quality level)?

[Scarpa]

Also, for some reason the dump from DF acts a bit glitchy sometimes with the Mayday set.

Sometimes when I try to dump the map to the application, it gives me the suppourted version not found error, but when I move around a bit or something, it goes through. I have no idea why it does this because it does load the map, but moving around a bit or unpausing/pausing gets it to work after a bit of fiddling around.

I didn't reply as I couldn't think of anything useful to say, I can't think of anything that would cause this error. If I get time before the next release I'll add some fallback code and I'll test it with the Mayday set (not that it should make any difference). Are you running on a multi-core system? Are the apps both running on the same core?

I had the same issue yesterday with an unmodded version of d11. The only changes were a character set and some init changes. I had to try about 4 or 5 times to get it to recognize the DF process. I do have a multi-core machine so next time it occurs I'll investigate a little closer.

[Jay]

Vista (and Windows 7?) has an anti-hack feature that's impossible to disable and randomizes addresses in executables that allow it.  It's quite possible that's the cause here, since none of you have mentioned an OS (>.<)
I don't remember the specifics, but you can force DF to not allow it via hex editing, mentioned in one of the earlier 3rd party tool threads.

[Scarpa]

I already did the hex editor trick to use Khazad and 3Dwarf. I don't think that's the issue.

In this case I had dumped the map, took a screenshot, closed VisualFortress, then after about 20 minutes tried again and it wouldn't recognize DF. I hadn't closed DF at all during the whole process.

I did have Dwarf Manager running in between but I'm not sure how that could affect it. I'll try to get better info if it happens again.

[Baboonanza]

I should have taken taken care of the Vista ASLR. I've certainly never had this problem during testing on Vista or XP.

Re-model LOD: It would be best in seperate files for each LOD, but it's easy enough to do it myself.

The release is a bit delayed at the moment. I've written all the necessary code and I'm just debugging it. I'm away from Saturday next week so hopefully I'll get it out by them.