TerrainView 1.54 bug... anyone seen this before?

[Quicksilver]

I got the latest v1.54 of TerrainView from here a few days ago, and noted that the segments I export with this version are completely corrupt!

[Quicksilver]

<BUMP>

Anybody? At least tell me it's just my problem...

[Snake Man]

This is really stupid post from me but... I don't know. Never used export yet on v1.54 but I'll try to look into this

PMC TFW
Snake Man

[hduman]

Cihat and I had the same problem when we were trying to develop a 128 x 128 campaign. When we ran SPTinstall or NPTinstall to generate L* files out of theater.L2, I saw 5 digit elevation values just next to zeroes. That's why we gave up working on 128 and concentrated on 64 size campaign. I assumed that either we skipped something in the theater tutorial or it stemmed from SPTinstall.exe file. We tried it over and over, but no way.

So, quicksilver you are not alone...

DUMAN is out....

[Snake Man]

quote:Originally posted by DUMAN:
When we ran SPTinstall or NPTinstall

So which one it was as?

PMC TFW
Snake Man

[Malc]

Snake Man,

I have seen this too, and also put it down to something I was doing. Not so sure SP or NT terrain builder has anything to do with it.

Its a definite problem with the import/export routine in v1.54

[hduman]

Snake Man,

The installer program I used was SPTinstall.exe. I will try to go through the same process and attach the snapshots of the 128 size terrain I could not make it work.

DUMAN is out for now...

[Malc]

Now I'm really fed up...! I done a fair chunk of tiling at work over the last week. I sent it home to import into my master .L2 and to my dismay, I got this...



Does anyone know of a 4-byte Terrainview version where the import function works? I have tried 1.53 and 1.54, but neither are working.

[Quicksilver]

OK guys, first things first.

There are TWO different versions of TerrainView available, since v1.53, each one for 64- and 128-type theaters.

The same goes fot TInstall too, 2 different versions there as well. Make sure you're using the right one.

Now, if I remember correctly, in the v1.54 zip file, there was only ONE version of TView. Could it be that this was the 128-compatible one? (mind you, I'm not really sure about this, there might be 2 files in there...)

Anyway, just an idea. And Malcom, as for that message you get... I think it's what you get when you try to import segments from a pre-1.48 version of TV to a newer one. Codec changed the export format from v1.48 and afterwards. That's why I keep two versions of TV... just in case... )

[Malc]

quote:Originally posted by Quicksilver
There are TWO different versions of TerrainView available, since v1.53, each one for 64- and 128-type theaters.

This is not true... TERRAINVIEW.EXE is for 2-byte .L2 files while TERRAINVIEWLG.EXE is for 4-byte .L2 files

Can't agree with rest of your post either... the error window I posted is what happens when I try to import a series of segments from TERRAINVIEWLG.EXE I have installed at work on a Windoze 2000 SP3 machine to the TERRAINVIEWLG.EXE installed on a Windoze 2000 SP3 machine I have at home.
Both the work and the home .EXE came from the same zip downloaded from here at PMC. The error message only occurs with ...LG.EXE version 1.53 and 1.54 - the standard 2-byte version works fine.

It has nothing at all to do with Tinstall - this I can be absolutely sure of!

[Quicksilver]

quote:Originally posted by Malcolm Hutcheon:
This is not true... TERRAINVIEW.EXE is for 2-byte .L2 files while TERRAINVIEWLG.EXE
is for 4-byte .L2 files

I thought that was the same thing? 2-byte for 64-seg theaters, and 4-byte for 128-seg ones...

Anyway, I haven't worked with Terrainviewlg.exe, so I can't think about anything else.

Seems to me that mr.Onions could take a look and help us all here!

[Snake Man]

Guys guys...

2 byte is what we developers work on!

4 byte is the version for in-game files!

There is NO utility (well besides Terrainview Large) that handles 4 byte theater.L2 file, so do all your work on 2 byte L2 file and when you need to test in falcon run the LODFixer and convert it to 4 byte. Remember to keep the original 2 byte in safe place.

As I'm using CATE, there really is no "original 2 byte" version as I can always re-create it with CATE. I must say I've done it hundreds of times to ODS L2 for example.

Forget working on 4 byte theater.L2 files!

PMC TFW
Snake Man

[Quicksilver]

All right SM, thanks.

So, back to the original topic: is there a problem with the TView 1.54 Export function? Or is it a matter of using the wrong version of TV?

[Quicksilver]

DOH! I finally figured it out! Damn it, I'm an idiot!

Sorry for the mess ladies & gentlemen...

[Snake Man]

quote:Originally posted by Quicksilver:
TView is for .l2 files that HAVE NOT gone through Tinstall or LodFixer, and TViewLG is for files that HAVE been run through this!

Uh?

That's what I said in the previous post:

quote:
Guys guys...
2 byte is what we developers work on!

4 byte is the version for in-game files!

quote:I guess TView 1.54 is perfectly OK

Terrainview v1.54 actually does not work ok on export & import segments feature. At least when I opened (yes regular TV to 2 byte L2) ODS L2, exported few segments and then imported them back in. It was all garbage.

I have sent screenshot of the problem to Codec already so lets see how it turns out.

PMC TFW
Snake Man

[Quicksilver]

quote:Originally posted by Snake Man:
Uh?
That's what I said in the previous post:

Yes... that's why I said "DOH". I finally understood what you were saying!

quote:Originally posted by Snake Man:
Terrainview v1.54 actually does not work ok on export & import segments feature.

Ah! Good thing that I've kept a backup of TV1.53 then (next to my old v1.47... you know, in case I get a *very old* segment...)

Let's see what Julian has to say then.

[Malc]

quote:Originally posted by Snake Man:
Terrainview v1.54 actually does not work ok on export & import segments feature. At least when I opened (yes regular TV to 2 byte L2) ODS L2, exported few segments and then imported them back in. It was all garbage.

I have sent screenshot of the problem to Codec already so lets see how it turns out.

PMC TFW
Snake Man

That is wierd... I have no problem importing/exporting using TV153 or 154 when working with 2-byte, but I also get the garbaged stuff when doing it with TVLG153 and 154.