• 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.

P3D v5 Does CreateTVecFreewayTraffic work in scenProc v3.3?

Messages
1,635
Country
unitedstates
Very simple script. No errors and I see it creates 10 shapes (that matches my data in QGIS). But no traffic appears? Here's the script:

Road traffic script using P3Dv4 shp2vec - error free but no traffic.jpg


That was using shp2vec from P3Dv4. So I tried P3D v5 and got the following error.

Road traffic script using P3Dv5 shp2vec - error anamoly.jpg


funny I would have thought v4 maybe would get the error. Anywho no luck either way. Any ideas? (May have to try SBuilder if scenProc does not work?)

THx, Marcus
 
scenProc can generate traffic data with no problem, you can also do bidirectional traffic,
if i recall you need to specify complexity which traffic data appears, and make sure complexity slider is set to that threshold for traffic data to show in sim.


Code:
ImportOGR|B:\FL\Section_36\Roads_FL_Q55_mot.shp|*|*|AUTODETECT

# Format: CreateTVecFreewayTraffic|filter|defaultLanes|oneWay|laneAttr|complexity
# 2 = default lanes, F = assume two-way, lanes = actual lanes from attribute
# 5 = scenery complexity (Very Dense and above)
CreateTVecFreewayTraffic|fclass="motorway"|2|F|lanes|5

ExportTVecBGL|B:\FL\Section_36\Road_Traffic_FL_Q55_mot_road_traffic|FL_Q55_mot_road_traffic
 
Last edited:
Hi,

The shp2vec in recent P3D SDKs is broken, so that explains why v5 gives the error. But if you use an earlier P3D SDK it should work fine.

How much traffic is shown in the simulator is also influenced by the population density specified in the default scenery. Is the area where you are making the traffic very sparse?
 
Thx for the quick replies guys. Ok, so use P3Dv4 version (maybe P3Dv3), check. The road is a motorway with the population over 2000 per square mile so I should see something I would think. I have the traffic slider at its highest setting. Plenty of traffic all around that motorway on residential and other roads. I will try the arguments you posted Chris '2|F|lanes|5' and see if that makes any difference. Maybe I have to at least put a minimum # "5" for it to even show.

UPDATE - well, I think I know what is happening. If I select 'All Roads' nothing will appear on the motorway, with or without my file. If I select 'Freeways Only' then I do get lots of traffic on the motorway, with or without my file. This is using my photoreal scenery on top or default ground. Either way.

If I have my photoreal scenery on, there is no motorway traffic but in the default ground leading right up my scenery there is motorway traffic which then cuts off right at the beginning of my scenery. If I select all roads I get plenty of traffic all around but very little on the motorway on default scenery and no motorway traffic on top of my scenery.

Oh well, not sure how to work around that. Interesting observation though.
 
Last edited:
It's not the Traffic slider that determines whether the traffic shows up—it's the Scenery Complexity slider that acts as the first trigger.

In your script, the "5" setting refers to the required Scenery Complexity level. Only when that slider is set to the threshold (or higher) will the traffic data become active. Once it's triggered, then the Traffic slider controls the density.

So to be clear:
  • Scenery Complexity determines whether traffic appears at all.
  • Traffic slider affects how dense that traffic is.
Without the correct Scenery Complexity level, the traffic won't show up—regardless of the Traffic slider setting.
 
No, that attribute 5 has nothing to do with the scenery complexity. The last two attributes specify the attribute (lanes) that is used to read the number of lanes from and when no such attribute exists on the feature it uses a default of 5.

Adding your photorealistic should not alter the traffic that is present. Or does your scenery also have an exclude to remove the default traffic?
 
FYI - Scenery Complexity was also set to its highest setting. From I gather, it seems like there is a certain amount of traffic available. Instead of adding additional traffic when you select 'all roads', it seems to divide up what traffic there is available to all the other roads, leaving little left for the motorway. At least that's what it looks like on my system. I wonder if the length of the road has anything to due with the amount of traffic? Maybe a short length of motorway has no time to build up traffic as we know the vector lines are never continuous. No longer an issue as I now know my file works but just an interesting observation.
 
Back
Top