Feature #5890

Tool to create object template pew to ease object definition in v3.

Added by kju almost 6 years ago. Updated over 5 years ago.

Status:Closed Start date:11/16/2009
Priority:Normal Due date:
Assignee:mikero % Done:

0%

Category:-
Target version:Completed
Affected Version:

Description

As discussed in Skype.

Ability to create a simple PEW that defines a desired list of objects.
Possible input format:

1 TYPE;"OBJECT"; 2 artifical;"ca\buildings\houseX";

The tool should create a dummy PEW that only contains the object
definitions.

History

Updated by mikero almost 6 years ago

  • Status changed from Assigned to In progress
  • Target version set to Work in progress

CreatePewObjects v1.00 now on site

It will E)xport from a suite of pew files to (effectively) create a 'library' of pew objects, the so-called template.

this library is in humanly readable text form in classic class statements and should be easily ammended by hand if required.

the 'library' created can be A)dded or I)mported to a pew of choice. Whether the pew-of-choice has layers (rvmat materials) and / or already existing objects is your call.

Updated by kju almost 6 years ago

Great news! Cheers :)

1) Without params it will create an memory error.

2) -E x.pew file should create a file.txt instead of a file.

3) The export from Utes looks good for aritifical,
though no nature objects in the export.

4) Possible to change the export data format from

1 class ObjectTemplates 2 { 3 class Object

to

1 class ObjectTemplates 2 { 3 class lhd_elev_r //strModelName

please?

It would make it easier to get an idea what was exported.

5) Every object in the Utes export had these values:

1 ulObjectType= 2 ulMarkerType= 3 strModelFilename= 4 strModelName= 5 dblxyGeometryBounds[]= 6 dblxyResolutionBounds[]=

Is that correct?

Updated by mikero almost 6 years ago

class ObjectTemplates {
class lhd_elev_r //strModelName

this was in the original, unfortunately some names (or files) have spaces in them and cannot consequently be declared as classes. i will think about simply replacing with underlines..

"Every object in the Utes export had these values:"

there are some more, but if detected with default values (generally zero) eg, they are ignored as waste of space. the ones you see listed, are not default.

for a full list, see the readme

2) -E x.pew file should create a file.txt instead of a file

that. i leave entirely up to the user. I favoired .cfg myself or .obj or .exp But the user is free to do as they please

3) The export from Utes looks good for aritifical,
though no nature objects in the export.

that is because natural (plants) is the default. They, are not declated

new version on site which fixes the crash, and, completes roadnets and artifcial name calls.

please consider that the prime emphasis of this file is to generate 100% accurate copy of the working model template. It's humanly readable factor is a lesser consideration. Important, but not the end game.

thank u for testing

new version on site (+new dll for different reasons)

Updated by kju almost 6 years ago

Cool and agreed. Thanks!

Testing new version now.

Updated by mikero almost 6 years ago

  • Status changed from In progress to Resolved
  • Target version changed from Work in progress to Completed

task completed with createwrpobjects

Updated by mikero over 5 years ago

  • Status changed from Resolved to Closed

Updated by kju over 5 years ago

Once again huge thanks to you mikero for doing this tool!

Also available in: Atom PDF