DM scale

[monks]

Hello Aaron, I'm using L3DT to create some terrain for ME-DEM's upcoming article. I've got a question- not sure whether I'm doing something wrong here as it's been a while
I created a New Design Map (Design/Inflate (Blank).
The scale is set to 64 DM pixels at 20m resolution, giving a 4096 px sq DM. The scale is corect in the DM view.
I import the image overlay and save: : File > Save > Save project as.

I've done no work on it other than this.
I open up the project again and the scale is wrong- it has roughly halved it.
I'm thinking that a way around this is to generate the heightmap, then save the project- that way I can go into Operations > Heightfield and alter the horizontal scale right?. This shouldn't be necessary though should it?

//update: looking at the project settings, they are correct: 64x64 at 20m res.I tried generate heightfield and preview heightfield and the scale is incorrect in there also. Going into change horizontal scale, it is set at 40m. Changing post generate does indeed correct the project scale.

I think it is the project save that is causing the scale alteration.
Cheers,
monks

[Aaron]

Hi Monks,

Yep, this is a bug, and thank-you for the report. This one specifically occurs when you load a project that does not include a heightfield. Because the design map file does not store horizontal scale, L3DT adjusts the scale of the design map after the project is loaded, based on the size and scale of the heightfield. When there's no heightfield (a case I hadn't considered), the routine resorted to the default heightfield scale of 10m and exited quietly. I've fixed this properly for the 'final' L3DT v2.4.

Cheers,
Aaron.

[monks]

Ah- OK. For the time being I'll go with the generate heightfield work- around.

Cheers,
monks

[monks]

Aaron- I still have the problem with the scale being reset on re-opening a project- I don't know if this made it onto the todo list for fixes.
This is what I did:

New project: Design/Inflate blank
imported a heightfield, altered its size and scale.
Generated a DM from this.
After saving I close and re-open and the scale is back to the original wrong scale before I resampled in step 2 above.

My version:
Release no: 2.4 Rev. 15
Build date: 28-June-06

Cheers,
monks

[Aaron]

Hi Monks,

I fixed that bug as I understood it, but I did miss one factor: changing the heightfield resolution does not alter the value stored in the project settings. I'll upload a fix later today.

One other thing; creating a new project before you import a heightfield is redundant, as the import operation creates a new project.

Cheers,
Aaron.

[monks]

Great- I'll incorporate that info into the tut,

Cheers,
monks

[Aaron]

Fixed. Update on downloads page.

Aaron.

[monks]

It's still doing it...stands behind his custard pie shield...could you post a quickie walkthrough on this to make sure that it isn't me?

I've tried both the same method as last time and also opening L3DT and simply importing a heightmap (rather than going through New Map).

version:
Large 3D Terrain (L3DT)

Release no: 2.4 Rev. 16
Build date: 03-July-06

Cheers,
monks

[Aaron]

Hi Monks,

Okay, this is what I tried:

Open L3DT
Import heightfield
Operations->Heightfield->Resample map (if required)
Operations->Heightfield->Set horiz scale (to desired value - important!)
Operations->Design map->Generate from HF
File->Save project
Close L3DT

Open L3DT
File->Open project
Scaling is still OK

Does this match your work-flow, or have I missed something?

Cheers,
Aaron.

[monks]

Hi Aaron, I think it's the .bt terrain. I've just tried the sequence with the .bt and it's still the same. I tried the same sequence with a TG and it works.
The .bt file is fine- no corruption, so it might be at L3DT's end?

I've emailed the file to you.

Cheers,
monks

[Aaron]

Ah, right you are!

The problem was in the handling of georeferencing in the BT loader/saver. I'll upload another fix in a day or two.

Cheers,
Aaron.

[monks]

-thought I ws losing my marbles there for a minute.
I'll go with the TG for now. I was using a .bt because that's the format of choice for us.

Cheers,
monks

[Aaron]

Hello,

It seems I was being a little optimistic when I said 'a day or two'. To fix this properly, I'll need to deepen the support for georeferencing in L3DT, and that might take a week or two.

Cheers,
Aaron.

[monks]

OK, no worries. The TG is fine,

Cheers,
monks