• Which the release of FS2020 we see an explosition of activity on the forun and of course we are very happy to see this. But having all questions about FS2020 in one forum becomes a bit messy. So therefore we would like to ask you all to use the following guidelines when posting your questions:

    • Tag FS2020 specific questions with the MSFS2020 tag.
    • Questions about making 3D assets can be posted in the 3D asset design forum. Either post them in the subforum of the modelling tool you use or in the general forum if they are general.
    • Questions about aircraft design can be posted in the Aircraft design forum
    • Questions about airport design can be posted in the FS2020 airport design forum. Once airport development tools have been updated for FS2020 you can post tool speciifc questions in the subforums of those tools as well of course.
    • Questions about terrain design can be posted in the FS2020 terrain design forum.
    • Questions about SimConnect can be posted in the SimConnect forum.

    Any other question that is not specific to an aspect of development or tool can be posted in the General chat forum.

    By following these guidelines we make sure that the forums remain easy to read for everybody and also that the right people can find your post to answer it.

Problem Annotator e AGN file....

A

Anto80

Messages
119
Country
italy
:confused:

Hello Arno, I have a problem with annotator;
when I load a scenario to change or correct your files AGN made ​​with scenproc, the light poles (object library) | {0017a236-464f-14fd-f77f-2996fed44864} | are not displayed and there is no error messages, if I do not save anything
FSX in the light poles 8x8 normally see.
But if I annotator changes to buildings or vegetation, except for the work in fsx the poles disappear and are not seen, lost.

The same thing happens to you? Or is it just my problem?


Thank you.
Antonio.
 
Hi,

Yes, I have also seen that annotator does not show library objects. I'll check if it has something to do with the way the agn file is written.

Send from my phone using Tapatalk, so excuse the short sentences and possible typos
 
Hello, today I noticed that the polygons of vegetation have the same fate
if you load and save in annotar you also lose the data of vegetation such as light poles, among other things I had already mentioned that the polygons of vegetation were not appearing in annotator, or at least most of them.

The strange thing is that with AGN Merge Tool if you load a agn done with scenproc
you can see both poles of the lights that the polygons of vegetation that are not seen in annotator, of course, before you save with the annotator.

Have a nice day.

Antonio.
 
Last edited:
Hi,

I think I found what was wrong with the library objects. In the next development release (tomorrow) it should be fixed. For my test area library objects and vegetation polygons are showing fine in Annotator now.

Let me know if it also works for you,
 
:)

Hi, this is a great news, I'll try tomorrow and let you know the release if it works well ...

Thank you.
Antonio
 
:)

Hi Arno, excellent i have downloaded senproc, I did some tests and it seems to work well,
now in annotator can also see the poles (object library) and also saving the file agn are correct and you always see, are no longer deleted as before, now you can also correct the autogen without losing data.

I have not checked for vegetation, but she seems to have no more the problem than before.

Thank you again.
Antonio.
 
:confused:


Hi Arno, I found another problem, I do not know if there was even before the release of yesterday because I could not see the light poles in annotator, now moving a light pole below if there is another? In practice are double in the same position.
The problem is not present in all the streets with light poles but in some, if it is present all over the road is the same defect.
I noticed it because flying lights made ​​with the particle effect appeared ugly to look at, and the performance of the PC / FSX were down because of too many lights
(almost twice).

Try to see if there is a defect to you ...

Antonio.
 
Hi,

Could it be that the vector data you used has two lines for the road? In that case the point features for the roads would also be generated twice while processing the data. That's the only condition I can think of to get two lights.
 
Hi, do you place the lines for the lights, I do not think twice because given
in some cases the lights are also up from 4 to 9 in the same point ....

Before the release does not seem to have noticed because the effect of particle light was perfect, I can not even try to replace the "old version of scenprog because I would not see in any case no point in light annotator to ascertain the defect.

I am attaching the file that I used.
Thanks for your help ....

Antonio.
 

Attachments

Ok, let me double check tomorrow if there is no bug in the tool somewhere. But I haven't noticed the double objects yet.
 
Hi, to be sure it's not a data problem areas that I did, I tried to make the area of your tutorial (Schiermonnikoog).
I put the lights on the roads "tertiary" and the result was error there too, in some ways one pole in the other 2 poles, 4 poles and even
in one way, one below the other .....
In annotator selects the pole, move it and below are the others.
Place a shot .... areas ....

Antonio.
 

Attachments

  • palierrrore.jpg
    palierrrore.jpg
    306.3 KB · Views: 524
Hi,

Ok, I'll try to run the same test as you did with the data of that island. I'll let you know what I find.
 
Hi,

You found a couple of bugs actually :). I think I have fixed them now. There was a problem with the splitgrid step for line features and also the place points along line step did not calculate the remaining distance to the next point correctly in all cases. That should all be fixed now and I don't have duplicate points anymore.
 
:)

Ok tell me when is the release of scenproc to correct these bugs.

I would have another question to ask you, on a map that I'm trying data
of power lines, as I write strings to display them?


The labels are:
cables: 3
name: St. Joseph - Portoferraio
operator: Terna
power = line
ref: 048
VOLTAGE: 132000
wires: single
for the line

and
power = tower
ref = 70
to the point

I would like to put ag_highpower what should I write in CREATEAGNLIBOBJ and PLACEPOINTSALONGLINE
Always possible.

Thank you.
Antonio.
 
Hi,

A new development release is build automatically every night, so a new version with the changes is available already.

As far as I know there is no autogen class with only the highpower objects. That object is used in utilities of you look in the default.xml. But that also contains other objects. So it is not possible to place them directly, you would have to make a special autogen class.

Or you could try to place them as XML library objects.
 
Ok I downloaded the new release and the problem is solved, now the light poles are single, excellent.

For the power Line I thought about using this item:
<NAME> Z_Utilities </ NAME>
<NAME> Ag_HighPower </ NAME>
<GUID> 0b5dfe7540913c87701d68856e064a73 </ GUID>
which is located in default.xml library annotator, but actually is part of a group, thought enough puts the Guid.
Maybe I have a bit of confusion with the library annotator ....

However, if you want to use the data of the power line in the file OSM
I use and put the light poles to prove what should I write?
I already tried with the same parameters but does not display anything ...

example:
PLACEPOINTSALONGLINE | FTYPE = LINE, Power = line | 400 | 5 | type | power | hdg
CREATEAGNLIBOBJ | FTYPE = POINT, type = power | {0017a263-464f-14fd-f77f-2996fed44864} | hdg | 6, 6

But it does not work ........ it was just to try ....;)

Antonio.
 
Hi,

Do you see in the log that point features were created?

Filters are case senstive so Power=line is not the same as power=line. I think you need the last.
 
:D;)

I'm so sorry .... but I forgot to add label power on:

IMPORTOSM | elbacentro.osm | * | highway; landuse, building, power

now it works ......

Have a good weekend.

Antonio.
 
You must log in or register to reply here.
Back
Top