Freeway Traffic

[scruffyduck]

That's very strange that they show in TMFViewer but not in the sim.

Jon let me ask; in your TMFViewer, View menu|Vector Data|Exclusions, are Exclusions checked?

Rhett - if you mean under Vector Data|Layers then Yes Exclusions is checked

 

[scruffyduck]

<shapes>
<freeway>
<guid>
{54b91ed8-bc02-41b7-8c3b-2b8449ff85ec}
</guid>
<coordinates>
-83.5625964080552,34.1646846933103,0
-83.5504362729453,34.1695438429591,0
</coordinates>
</freeway>
</shapes>

Jim just to note that this xml is created to be used by Xml2Shp made by Winfried Orthmann

 

[GHD]

I could be wrong but the TMFViewer in Jon's picture above may only be the feature attributes of the table that associate with the DBase file and not the Shape file.

Jim,

TmfViewer reads only the cvx.bgl which is a combination of all four files, .xml, .dbf, .shp and .shx. If any one of these files were missing/incorrect shp2vec wouldn't convert them to a .bgl.

George

 

[scruffyduck]

Jim,

TmfViewer reads only the cvx.bgl which is a combination of all four files, .xml, .dbf, .shp and .shx. If any one of these files were missing/incorrect shp2vec wouldn't convert them to a .bgl.

George

Seems very odd that TmfViewer reads the bgl file as specificed by ADE but it does not display in FSX. So there must be a difference in the bgl file that is enough to stop the display but the source is good enough that Shp2Vec does not raise any error. Also it is worth saying that ADE can generate other shape vectors such as roads without a problem.

 

[jvile]

Originally Posted by jvile
<shapes>
<freeway>
<guid>
{54b91ed8-bc02-41b7-8c3b-2b8449ff85ec}
</guid>
<coordinates>
-83.5625964080552,34.1646846933103,0
-83.5504362729453,34.1695438429591,0
</coordinates>
</freeway>
</shapes>

Jim just to note that this xml is created to be used by Xml2Shp made by Winfried Orthmann

Thanks Jon

That answered that for me. I thought Winfried had done some work in the XML area.

 

[jvile]

Jim,

TmfViewer reads only the cvx.bgl which is a combination of all four files, .xml, .dbf, .shp and .shx. If any one of these files were missing/incorrect shp2vec wouldn't convert them to a .bgl.

George

Thanks George

I had a feeling the XML code was a combination of all 4 files combined but just wanted to be sure I was not overlooking something.

 

[Mace]

Seems very odd that TmfViewer reads the bgl file as specificed by ADE but it does not display in FSX. So there must be a difference in the bgl file that is enough to stop the display but the source is good enough that Shp2Vec does not raise any error. Also it is worth saying that ADE can generate other shape vectors such as roads without a problem.

My thought, earlier, was that maybe there is an exclusion poly set to exclude the FreewayTraffic GUID.

But since you had TMFViewer set to display all exclusion polys then I see none that would seemingly affect your FreewayTraffic based on what I see in your screenshot.

Matthew Styles (author of FSX_KML) has FreewayTraffic working, although admittedly I have never delved into the "how" of his method. He does use Shp2Vec.

There are also no problems with the close proximity of FreewayTraffic to an airport or the gmax objects or autogen. I have a WIP scenery of MHTG and it has the roads right next to the airport and around autogen and they are full of traffic.

So that rules that out.

 

[meshman]

withdrawn.

 

[DougMatthews]

This is too techy for me, but I'll try to explain what I've seen. Used ADE to set up a road and freeway traffic, road shows but no cars. Went and did the same in SBX, road and traffic shows, even if it's on the wrong side...

Looked at the DBF files spit out by both and see one difference. ADE, using XML2SHP, spits out a three field record; UUID, Direction and # of lanes.

ADE seems to result in the creation of a Shapefile that is correct. It has all the required fields. You can verify this by comparing it to the sample Shapefiles provided with the FSX Terrain SDK.

SBX spits out a four field record; UUID, Direction, # of lanes and GUID.

SBX seems to result in the creation of a Shapefile that has one extra field (the field named GUID), which will be ignored by Shp2Vec. None of the current (FSX) flavors of vector data need to have a field named GUID.

The SDKs state that the UUID should be the same as the GUID, or something to that effect.

If it truly says that, please let me know where.

So when XML2SHP is suppose to be passing the line <Field name="Uuid" type="GUID" /> there is nothing in the DBF record to pass.

?

In SBX using a "T" and a "F" both show in the DBF that the GUID of the record is the same as the GUID of the effect. So it gets compiled.

Again, the GUID field should not even be there.

Why Shp2Vec isn't showing any ill effects from not having the properly passed UUID = GUID is wayyyy beyond my knowledge. But me thinks if the DBF file gets structured "correctly" you'll get the correct parameters passed and traffic showing as it should.

But I've been wrong before, so this won't be the first time!

ADE seems to be doing everything correct. SBX has an extra field, which is ignored. SBX also has geometry of type PolylineZM, with the Z (elevation) and M (measure) both being zero. ADE's geometry matches that of the SDK samples - Polyline with no ZM. Both result in BGL files with seemingly valid Freeway Traffic vectors (validated using TmfViewer).

So far I'm at a loss as to why the ADE generated file would not work in-game. If I learn more I'll post.

-Doug

 

[DougMatthews]

If the SDK statement is true pertaining to F and T (forget B) what am I missing in the following XML and if I am missing the traffic direction how does it nest


<shapes>
<freeway>
<guid>
{54b91ed8-bc02-41b7-8c3b-2b8449ff85ec}
</guid>
<coordinates>
-83.5625964080552,34.1646846933103,0
-83.5504362729453,34.1695438429591,0
</coordinates>
</freeway>
</shapes>


I could be wrong but the TMFViewer in Jon's picture above may only be the feature attributes of the table that associate with the DBase file and not the Shape file.

The DBase file is part of the Shapefile. A Shapefile is made up of (at minimum) one .shp file (containing the geometry), one .shx file (containing the index) and one .dbf file (containing the attribute data).

-Doug

 

[scruffyduck]

Thanks Doug - I am really starting to go around in circles now and have run out of things to check. Would a copy of the cvx bgl file produced by ADE be of any help?

 

[DougMatthews]

Thanks Doug - I am really starting to go around in circles now and have run out of things to check. Would a copy of the cvx bgl file produced by ADE be of any help?

It might be helpful to have your file.

-Doug

 

[GHD]

Jon,

Can I suggest that you send all of the files, .xml, .dbf, .sxp, .shx and .bgl.

George

 

[scruffyduck]

Attached the full set of files for a very simple section of freeway as generated by ADE

Thanks Doug

 

[DougMatthews]

Attached the full set of files for a very simple section of freeway as generated by ADE

Thanks Doug

This is still on my radar, just have not had time to look deeper. Insanely busy around here right now.

-Doug

 

[scruffyduck]

Hi Doug

Many thanks - we have not managed to figure out what is happening so far

 

[bobbyjack]

Just thought I'd dust this off and ask how this is coming. Also, I must be missing something because I can not get roads or streams to show some of the time. Can these only be used at certian areas around the airport?

Bob

 

[scruffyduck]

Just thought I'd dust this off and ask how this is coming. Also, I must be missing something because I can not get roads or streams to show some of the time. Can these only be used at certian areas around the airport?

Bob

We still do not have a resolution for the freeway issue. We will be changing our method of generating this type of vector in a later version. I am not ware of any restrictions on roads or streams but one of the others may know more