How funny Mike!

I can't believe you saw those screenshots a year ago that I "snuck" into the forums, ha!  It actually is coming along quite well... of course taking way longer than I ever expected.  The encouragement I got there after posting made me decide to continue on.

I spent most of the past year coding to speed up the process as much as possible as we are dealing with 100's if not 1,000's of square miles.  But still takes a lot of manual input.  Started at the Mexican border and I am up to Oxnard/Ventura County right now heading east to the Colorado River.

Was debating to post a few more screenies this April Fool's day but did not want to remind simmers how long this simwestSOCAL "vaperware" has taken.

Oooops, sorry for taking the thread off course.  I do luv everything San Diego and this new airport does have some amazing airport rooftop detail.  Would like to see screenies of the frontside of the airport.

Great comparison video posted above.  That way simmers can decide which way to go. 

 

He's not the only one - Clutch - I recall being duly impressed and have wondered about them many times since...

Regards,

Scott

Ha You too Scott!

With such devotion you both have made my beta team if interested when the time comes....

Absolutely, wouldnt mind helping you out with some testing when that time comes.

mike

Would  it look better than this without installing  Orbx California Region?  I currently have Mega Scenery So9 cal and Night environment Caly and a whole bunch of adds for the San Diego city and KSAN...  I don't intend to get Orbx region for California.  because of the terrain, I prefer phto texture merged with augoten from the old So Cal *MS).

 

As you can see, I am flying the CS727.. Not the FsLabs A32x nor the PMDG's aircrafts. 

 

 

 

On 3/30/2017 at 8:40 PM, Clutch Cargo said:

I have to agree with Ron's comments on this one.  I live in San Diego and felt the area has an overall dark, "gloomy" feel to it.  Maybe it's the heavy shadowing of the airport and the downtown buildings.  San Diego is bright and sunny.  :)

Coronado agn have all flat roofs and sparsely any vegetation?  Approaching felt a little like a concrete jungle (like as if I was in LA, ha!), ...  again more trees would have helped.  While the modeler is definitely gifted, I see no reason to move on from my Latin VFR version.  But I am sure it will still sell well.

Clutch

I was looking forward to this product and planned to buy it the first day, but the negative comments, particularly about the dark downtown buildings, have put me off while I re-evaluate. I have visited San Diego, but it was many years ago before much of the "Manhattanization", and I don't recall it appearing dark and gloomy. I have re-looked at ORBX's preview screenshots and see the downtown is indeed dark and gloomy. I decided to look at the area on Google satellite and Earth views. It is clear that the Google shots were taken mid morning as the shadows are on the North and West sides of the skyscrapers, and they do indeed look dark and gray and similar to the ORBX screenshots looking at the city from the North West (where the airport is situated).   Also many of the ORBX sceenshots are under partly cloudy conditions, and cloud shadows darken parts of the landscape.  Here is a link to the Google views:

https://www.google.co.uk/maps/@32.718537,-117.1853569,2212a,35y,90h,38.89t/data=!3m1!1e3

I also noticed on the Google satellite views that with the urban sprawl, much of the rooftop views are in fact gray and white. But there seem to be a good scattering of red tile roofs, particularly to the West of the airport.

So I am wondering if those who have the ORBX airport have looked at the lighting under different weather and time of day situations, to see how the lighting and shadowing change the appearance of the cityscape (if they do).

 

On 3/29/2017 at 7:53 PM, Hoang Le said:

Very happy to hear that, did you manage VAS when flying there? With FSLabs A320x/PMDG 737 and LatinVFR KSAN, no ORBX products I have about 700-800MB free after landed there.

I finally got time for a couple of flights - one with FSX and one with P3D -

FSX - A little less than your VAS readings but basically the same with the PMDG737 (click on spoiler for hidden log and scroll down for summary):

Spoiler

 72125 G:\FSX\SimObjects\Airplanes\PMDG 737-800NGX WL\B737-800WL.AIR
    91688 Monitor IPC:024C (S32) = 3239600
    92188 Monitor IPC:024C (S32) = 3229376
   102250 Monitor IPC:024C (S32) = 2898988
   112297 Monitor IPC:024C (S32) = 2927380
   122250 Monitor IPC:024C (S32) = 2839608
   132250 Monitor IPC:024C (S32) = 2477760
   142406 Monitor IPC:024C (S32) = 2109432
   142484 Aircraft loaded: running normally now ...
   142484 User Aircraft ID 1 supplied, now being used
   143469 System time = 02/04/2017 10:28:55, Simulator time = 10:26:33 (17:26Z)
   143469 Aircraft="PMDG 737-800NGX PMDG House Winglets"
   152297 Monitor IPC:024C (S32) = 1596392
   162516 Monitor IPC:024C (S32) = 1514796
   173047 Monitor IPC:024C (S32) = 1403396
   182406 Monitor IPC:024C (S32) = 1263436
   191344 Starting everything now ...
   192422 Monitor IPC:024C (S32) = 1102772
   192500 Advanced Weather Interface Enabled
   212484 Monitor IPC:024C (S32) = 1095640
   252625 Monitor IPC:024C (S32) = 1068484
   262641 Monitor IPC:024C (S32) = 1044864
   272672 Monitor IPC:024C (S32) = 1006620
   282703 Monitor IPC:024C (S32) = 1055896
   292766 Monitor IPC:024C (S32) = 1033040
   302781 Monitor IPC:024C (S32) = 1026352
   312828 Monitor IPC:024C (S32) = 1004612
   322875 Monitor IPC:024C (S32) = 997784
   332891 Monitor IPC:024C (S32) = 998296
   373063 Monitor IPC:024C (S32) = 998288
   383141 Monitor IPC:024C (S32) = 998348
   433344 Monitor IPC:024C (S32) = 998884
   443359 Monitor IPC:024C (S32) = 998160
   453406 Monitor IPC:024C (S32) = 981464
   463453 Monitor IPC:024C (S32) = 961428
   473516 Monitor IPC:024C (S32) = 958116
   493578 Monitor IPC:024C (S32) = 958636
   503625 Monitor IPC:024C (S32) = 955012
   523719 Monitor IPC:024C (S32) = 956064
   543828 Monitor IPC:024C (S32) = 789796
   553875 Monitor IPC:024C (S32) = 762008
   563891 Monitor IPC:024C (S32) = 802216
   573922 Monitor IPC:024C (S32) = 743700
   584000 Monitor IPC:024C (S32) = 791540
   594031 Monitor IPC:024C (S32) = 830704
   604078 Monitor IPC:024C (S32) = 874500
   614094 Monitor IPC:024C (S32) = 840072
   624188 Monitor IPC:024C (S32) = 855388
   634203 Monitor IPC:024C (S32) = 876924
   644234 Monitor IPC:024C (S32) = 875988
   654281 Monitor IPC:024C (S32) = 879960
   664359 Monitor IPC:024C (S32) = 877132
   674375 Monitor IPC:024C (S32) = 871452
   684406 Monitor IPC:024C (S32) = 871556
   694438 Monitor IPC:024C (S32) = 944444
   704516 Monitor IPC:024C (S32) = 942744
   714547 Monitor IPC:024C (S32) = 940792
   724578 Monitor IPC:024C (S32) = 942768
   734625 Monitor IPC:024C (S32) = 954056
   744672 Monitor IPC:024C (S32) = 961468
   754734 Monitor IPC:024C (S32) = 959520
   764750 Monitor IPC:024C (S32) = 958516
   774781 Monitor IPC:024C (S32) = 958740
   784828 Monitor IPC:024C (S32) = 944644
   794922 Monitor IPC:024C (S32) = 944680
   804922 Monitor IPC:024C (S32) = 949816
   814953 Monitor IPC:024C (S32) = 963916
   824984 Monitor IPC:024C (S32) = 1062564
   845031 Monitor IPC:024C (S32) = 1062468
   855078 Monitor IPC:024C (S32) = 1141176
   865109 Monitor IPC:024C (S32) = 1141708
   885188 Monitor IPC:024C (S32) = 1138400
   945422 Monitor IPC:024C (S32) = 1148092
   985609 Monitor IPC:024C (S32) = 1147552
   995625 Monitor IPC:024C (S32) = 1145068
  1005656 Monitor IPC:024C (S32) = 1146720
  1015688 Monitor IPC:024C (S32) = 1143492
  1025734 Monitor IPC:024C (S32) = 1143432
  1035766 Monitor IPC:024C (S32) = 1142348
  1045813 Monitor IPC:024C (S32) = 1138968
  1055828 Monitor IPC:024C (S32) = 1139356
  1065875 Monitor IPC:024C (S32) = 1138336
  1075906 Monitor IPC:024C (S32) = 1143192
  1085938 Monitor IPC:024C (S32) = 1146044
  1096000 Monitor IPC:024C (S32) = 1144040
  1106047 Monitor IPC:024C (S32) = 1144176
  1116063 Monitor IPC:024C (S32) = 1182172
  1126125 Monitor IPC:024C (S32) = 1181748
  1136234 Monitor IPC:024C (S32) = 1184248
  1146234 Monitor IPC:024C (S32) = 1182728
  1156281 Monitor IPC:024C (S32) = 1183992
  1166328 Monitor IPC:024C (S32) = 1182904
  1176375 Monitor IPC:024C (S32) = 1183544
  1186422 Monitor IPC:024C (S32) = 1186324
  1196469 Monitor IPC:024C (S32) = 1185236
  1206500 Monitor IPC:024C (S32) = 1185908
  1236625 Monitor IPC:024C (S32) = 1184820
  1296859 Monitor IPC:024C (S32) = 1181296
  1326969 Monitor IPC:024C (S32) = 1186564
  1337000 Monitor IPC:024C (S32) = 1179716
  1397219 Monitor IPC:024C (S32) = 1179712
  1407219 Monitor IPC:024C (S32) = 1179716
  1447391 Monitor IPC:024C (S32) = 1178656
  1457422 Monitor IPC:024C (S32) = 1169380
  1477500 Monitor IPC:024C (S32) = 1178656
  1487547 Monitor IPC:024C (S32) = 1178636
  1547781 Monitor IPC:024C (S32) = 1225564
  1557797 Monitor IPC:024C (S32) = 1239448
  1567844 Monitor IPC:024C (S32) = 1254220
  1577891 Monitor IPC:024C (S32) = 1262412
  1608016 Monitor IPC:024C (S32) = 1292564
  1638109 Monitor IPC:024C (S32) = 1292512
  1698344 Monitor IPC:024C (S32) = 1289080
  1708391 Monitor IPC:024C (S32) = 1280564
  1738516 Monitor IPC:024C (S32) = 1211812
  1748547 Monitor IPC:024C (S32) = 1212428
  1758609 Monitor IPC:024C (S32) = 1213872
  1788719 Monitor IPC:024C (S32) = 1220332
  1828875 Monitor IPC:024C (S32) = 1218528
  1869031 Monitor IPC:024C (S32) = 1209900
  1879078 Monitor IPC:024C (S32) = 1218528
  1899156 Monitor IPC:024C (S32) = 1217052
  1908531 *** G3D bad pointer trapped and crash prevented ***
  1909234 Monitor IPC:024C (S32) = 1216108
  1919281 Monitor IPC:024C (S32) = 815904
  1939344 Monitor IPC:024C (S32) = 815188
  1949422 Monitor IPC:024C (S32) = 812708
  1959453 Monitor IPC:024C (S32) = 806824
  1969547 Monitor IPC:024C (S32) = 777028
  1979563 Monitor IPC:024C (S32) = 771620
  1989578 Monitor IPC:024C (S32) = 772736
  1999688 Monitor IPC:024C (S32) = 766580
  2009703 Monitor IPC:024C (S32) = 749832
  2019766 Monitor IPC:024C (S32) = 743228
  2029797 Monitor IPC:024C (S32) = 730796
  2039859 Monitor IPC:024C (S32) = 730068
  2049906 Monitor IPC:024C (S32) = 727000
  2059984 Monitor IPC:024C (S32) = 717092
  2070016 Monitor IPC:024C (S32) = 715120
  2080094 Monitor IPC:024C (S32) = 707220
  2090141 Monitor IPC:024C (S32) = 708628
  2100156 Monitor IPC:024C (S32) = 670564
  2110234 Monitor IPC:024C (S32) = 657152
  2120313 Monitor IPC:024C (S32) = 635852
  2130297 Monitor IPC:024C (S32) = 607988
  2140328 Monitor IPC:024C (S32) = 687476
  2150406 Monitor IPC:024C (S32) = 729756
  2160422 Monitor IPC:024C (S32) = 711628
  2170500 Monitor IPC:024C (S32) = 724972
  2180563 Monitor IPC:024C (S32) = 704624
  2190641 Monitor IPC:024C (S32) = 638284
  2200672 Monitor IPC:024C (S32) = 642604
  2210750 Monitor IPC:024C (S32) = 638508
  2220781 Monitor IPC:024C (S32) = 643908
  2230859 Monitor IPC:024C (S32) = 644508
  2240922 Monitor IPC:024C (S32) = 645528
  2250969 Monitor IPC:024C (S32) = 642696
  2260984 Monitor IPC:024C (S32) = 650648
  2271047 Monitor IPC:024C (S32) = 640028
  2281094 Monitor IPC:024C (S32) = 716308
  2291141 Monitor IPC:024C (S32) = 713972
  2301172 Monitor IPC:024C (S32) = 713208
  2311219 Monitor IPC:024C (S32) = 676140
  2321281 Monitor IPC:024C (S32) = 656308
  2331344 Monitor IPC:024C (S32) = 702532
  2341406 Monitor IPC:024C (S32) = 698856
  2351453 Monitor IPC:024C (S32) = 699408
  2352375 Sim stopped: average frame rate for last 2170 secs = 34.1 fps
  2352375    Max AI traffic was 375 aircraft (Deleted 0)
  2356141 === DLLStop called ...
  2356141 === Closing external processes we started ...
  2357141 === About to kill any Lua plug-ins still running ...
  2357297 === Closing global Lua thread
  2358297 === About to kill my timers ...
  2358500 === Restoring window procs ...
  2358500 === Unloading libraries ...
  2358500 === stopping other threads ...
  2358500 === ... Memory checking ...
  2358500 === ... Button scanning ...
  2358594 === ... Axis scanning ...
  2358703 === Releasing joystick devices ...
  2358703 === Freeing macro memory
  2358703 === Removing any offset overrides
  2358703 === Clearing any displays left
  2358703 === NOTE: not calling SimConnect_Close ...
  2358703 === AI slots deleted!
  2358703 === Freeing button memory ...
  2358703 === Closing my Windows ...
  2358703 === Freeing FS libraries ...
  2359703 === Closing devices ...
  2359703 === Closing the Log ... Bye Bye! ...
  2359703 System time = 02/04/2017 11:05:51, Simulator time = 11:02:43 (18:02Z)
  2359703 *** FSUIPC log file being closed
Minimum frame rate was 10.1 fps, Maximum was 72.0 fps
Minimum available memory recorded was 594Mb
Average frame rate for running time of 2186 secs = 34.0 fps
G3D fix: Passes 60134, Null pointers 0, Bad pointers 2, Separate instances 1
Maximum AI traffic for session was 375 aircraft
Memory managed: 1023 Allocs, 1023 Freed
********* FSUIPC Log file closed ***********

P3Dv3

Spoiler

101938 G:\Prepar3D v3\SimObjects\Airplanes\PMDG 737-800NGX WL\B737-800WL.air
   124407 Monitor IPC:024C (S32) = 2534328
   129516 Monitor IPC:024C (S32) = 2265116
   139485 Monitor IPC:024C (S32) = 1723108
   149985 Monitor IPC:024C (S32) = 1433256
   159672 Monitor IPC:024C (S32) = 1315528
   162375 Aircraft loaded: running normally now ...
   162375 User Aircraft ID 1 supplied, now being used
   163313 System time = 04/04/2017 11:34:06, Simulator time = 08:32:03 (15:32Z)
   163313 Aircraft="Boeing 737-832NGX Delta Air Lines Winglets"
   166391 Weather Mode now = Theme
   169532 Monitor IPC:024C (S32) = 859868
   175344 Starting everything now ...
   175422 ASN active function link set
   175422 Ready for ASN WX radar
   176688 Advanced Weather Interface Enabled
   179547 Monitor IPC:024C (S32) = 1170740
   189578 Monitor IPC:024C (S32) = 1116916
   199625 Monitor IPC:024C (S32) = 1097252
   209657 Monitor IPC:024C (S32) = 1060620
   219672 Monitor IPC:024C (S32) = 1061132
   229703 Monitor IPC:024C (S32) = 1061644
   249750 Monitor IPC:024C (S32) = 1041712
   259782 Monitor IPC:024C (S32) = 1042224
   269813 Monitor IPC:024C (S32) = 1043312
   279844 Monitor IPC:024C (S32) = 1042800
   289860 Monitor IPC:024C (S32) = 1042992
   299891 Monitor IPC:024C (S32) = 1033756
   309938 Monitor IPC:024C (S32) = 1033584
   319969 Monitor IPC:024C (S32) = 1028520
   330000 Monitor IPC:024C (S32) = 1030460
   340016 Monitor IPC:024C (S32) = 1022668
   350063 Monitor IPC:024C (S32) = 1023472
   360110 Monitor IPC:024C (S32) = 984220
   370157 Monitor IPC:024C (S32) = 978928
   380157 Monitor IPC:024C (S32) = 977980
   390203 Monitor IPC:024C (S32) = 976936
   400235 Monitor IPC:024C (S32) = 976204
   410266 Monitor IPC:024C (S32) = 973888
   420282 Monitor IPC:024C (S32) = 960980
   430328 Monitor IPC:024C (S32) = 882828
   440360 Monitor IPC:024C (S32) = 900760
   450391 Monitor IPC:024C (S32) = 898668
   460453 Monitor IPC:024C (S32) = 903764
   470485 Monitor IPC:024C (S32) = 902796
   480500 Monitor IPC:024C (S32) = 901660
   490532 Monitor IPC:024C (S32) = 903920
   500578 Monitor IPC:024C (S32) = 909584
   510610 Monitor IPC:024C (S32) = 898168
   520625 Monitor IPC:024C (S32) = 903316
   530657 Monitor IPC:024C (S32) = 895536
   540703 Monitor IPC:024C (S32) = 1006708
   550735 Monitor IPC:024C (S32) = 1005116
   560782 Monitor IPC:024C (S32) = 1004048
   570828 Monitor IPC:024C (S32) = 987888
   580860 Monitor IPC:024C (S32) = 969724
   590907 Monitor IPC:024C (S32) = 991280
   600953 Monitor IPC:024C (S32) = 991196
   610969 Monitor IPC:024C (S32) = 990764
   621016 Monitor IPC:024C (S32) = 990736
   631047 Monitor IPC:024C (S32) = 1011956
   641078 Monitor IPC:024C (S32) = 1012516
   651110 Monitor IPC:024C (S32) = 1011988
   661141 Monitor IPC:024C (S32) = 1012840
   671172 Monitor IPC:024C (S32) = 1013872
   681203 Monitor IPC:024C (S32) = 1014428
   691235 Monitor IPC:024C (S32) = 1013404
   701266 Monitor IPC:024C (S32) = 1012880
   711297 Monitor IPC:024C (S32) = 1012960
   721328 Monitor IPC:024C (S32) = 1013512
   731360 Monitor IPC:024C (S32) = 1011852
   741391 Monitor IPC:024C (S32) = 1011860
   751422 Monitor IPC:024C (S32) = 1012344
   791563 Monitor IPC:024C (S32) = 1015108
   801610 Monitor IPC:024C (S32) = 1017736
   851797 Monitor IPC:024C (S32) = 1011128
   861813 Monitor IPC:024C (S32) = 1007848
   881907 Monitor IPC:024C (S32) = 1015640
   912000 Monitor IPC:024C (S32) = 998936
   922047 Monitor IPC:024C (S32) = 1015320
   932078 Monitor IPC:024C (S32) = 1012180
   942110 Monitor IPC:024C (S32) = 1013844
   952172 Monitor IPC:024C (S32) = 1011124
   962203 Monitor IPC:024C (S32) = 1013808
  1012375 Monitor IPC:024C (S32) = 1014336
  1072594 Monitor IPC:024C (S32) = 1013952
  1082641 Monitor IPC:024C (S32) = 1014464
  1102703 Monitor IPC:024C (S32) = 1046224
  1112735 Monitor IPC:024C (S32) = 1119420
  1122782 Monitor IPC:024C (S32) = 1177488
  1132813 Monitor IPC:024C (S32) = 1161104
  1142844 Monitor IPC:024C (S32) = 1169296
  1152875 Monitor IPC:024C (S32) = 1165044
  1162907 Monitor IPC:024C (S32) = 1162932
  1172938 Monitor IPC:024C (S32) = 1163672
  1213094 Monitor IPC:024C (S32) = 1164752
  1233141 Monitor IPC:024C (S32) = 1155920
  1253219 Monitor IPC:024C (S32) = 1155224
  1263250 Monitor IPC:024C (S32) = 1154712
  1273282 Monitor IPC:024C (S32) = 1152524
  1283328 Monitor IPC:024C (S32) = 1153036
  1293375 Monitor IPC:024C (S32) = 1146572
  1303407 Monitor IPC:024C (S32) = 1133676
  1333516 Monitor IPC:024C (S32) = 1128688
  1343532 Monitor IPC:024C (S32) = 1127640
  1353563 Monitor IPC:024C (S32) = 1128740
  1363610 Monitor IPC:024C (S32) = 1128720
  1383672 Monitor IPC:024C (S32) = 1127616
  1393719 Monitor IPC:024C (S32) = 1126868
  1443875 Monitor IPC:024C (S32) = 1124868
  1453922 Monitor IPC:024C (S32) = 1123436
  1484032 Monitor IPC:024C (S32) = 1115444
  1494078 Monitor IPC:024C (S32) = 735456
  1504110 Monitor IPC:024C (S32) = 1088528
  1524188 Monitor IPC:024C (S32) = 1088016
  1534203 Monitor IPC:024C (S32) = 1088528
  1544266 Monitor IPC:024C (S32) = 1084224
  1554297 Monitor IPC:024C (S32) = 1076560
  1564344 Monitor IPC:024C (S32) = 1079808
  1574375 Monitor IPC:024C (S32) = 1079788
  1584407 Monitor IPC:024C (S32) = 1081504
  1594422 Monitor IPC:024C (S32) = 1080972
  1604485 Monitor IPC:024C (S32) = 1082028
  1614532 Monitor IPC:024C (S32) = 1081668
  1624641 Monitor IPC:024C (S32) = 1082684
  1634594 Monitor IPC:024C (S32) = 1082544
  1644672 Monitor IPC:024C (S32) = 1082652
  1654688 Monitor IPC:024C (S32) = 1081044
  1664735 Monitor IPC:024C (S32) = 1082096
  1674766 Monitor IPC:024C (S32) = 1078756
  1684844 Monitor IPC:024C (S32) = 1084180
  1694875 Monitor IPC:024C (S32) = 1079436
  1704907 Monitor IPC:024C (S32) = 1076924
  1714953 Monitor IPC:024C (S32) = 1077924
  1724985 Monitor IPC:024C (S32) = 1072336
  1735016 Monitor IPC:024C (S32) = 1059008
  1745078 Monitor IPC:024C (S32) = 1059520
  1755110 Monitor IPC:024C (S32) = 1061008
  1765141 Monitor IPC:024C (S32) = 1060616
  1775172 Monitor IPC:024C (S32) = 1060136
  1795266 Monitor IPC:024C (S32) = 1069168
  1805297 Monitor IPC:024C (S32) = 1075064
  1825391 Monitor IPC:024C (S32) = 1074552
  1835422 Monitor IPC:024C (S32) = 1074572
  1855469 Monitor IPC:024C (S32) = 1074600
  1865516 Monitor IPC:024C (S32) = 972348
  1875532 Monitor IPC:024C (S32) = 1018012
  1885610 Monitor IPC:024C (S32) = 1003760
  1895625 Monitor IPC:024C (S32) = 1020572
  1920313 Sim stopped: average frame rate for last 1757 secs = 52.3 fps
  1920313    Max AI traffic was 173 aircraft (Deleted 0)
  1947750 === DLLStop called ...
  1947750 === Closing external processes we started ...
  1948750 === About to kill any Lua plug-ins still running ...
  1948907 === Closing global Lua thread
  1949907 === About to kill my timers ...
  1950110 === Restoring window procs ...
  1950110 === Unloading libraries ...
  1950110 === stopping other threads ...
  1950110 === ... Memory checking ...
  1950110 === ... Button scanning ...
  1950203 === ... Axis scanning ...
  1950297 === Releasing joystick devices ...
  1950297 === Freeing macro memory
  1950297 === Removing any offset overrides
  1950297 === Clearing any displays left
  1950297 === Calling SimConnect_Close ...
  1950907 === SimConnect_Close done!
  1950907 === AI slots deleted!
  1950907 === Freeing button memory ...
  1950907 === Closing my Windows ...
  1950907 === Freeing FS libraries ...
  1951907 === Closing devices ...
  1951907 === Closing the Log ... Bye Bye! ...
  1951907 System time = 04/04/2017 12:03:54, Simulator time = 09:03:48 (16:03Z)
  1951907 *** FSUIPC log file being closed
Minimum frame rate was 18.8 fps, Maximum was 159.3 fps
Minimum available memory recorded was 718Mb
Average frame rate for running time of 1757 secs = 52.3 fps
Maximum AI traffic for session was 173 aircraft
Memory managed: 836 Allocs, 835 Freed
********* FSUIPC Log file closed ***********

For P3D (latest version), I had a max 159 fps w/AS16 and a little more than 1GB of VAS remaining.  For FSX the max was 72 and no real weather and about 700MB of VAS remaining.  In each case I had more than enough system power to run everything.

Best regards,

Jim

 

 

Hello,

Thanks Jim. I am slowly changing to P3D and for several days I have read through comments, pictures/videos comparing LatinVFR and ORBX. For now actually I like the way LatinVFR looks more, and it performs beautifully in my P3D. I have also read somewhere that LatinVFR is updating their San Diego. This shall be interesting.
Cheers,
Hoang Le

EDIT: officially confirmed by LatinVFR

Question:  as a heavy iron IFR flier, should I be considering the orbex socal?  How much would I see anyhow?  Would it be worth the fps and vas hit?

50 minutes ago, Boomer said:

Question:  as a heavy iron IFR flier, should I be considering the orbex socal?  How much would I see anyhow?  Would it be worth the fps and vas hit?

In my opinion, since you only fly heavy metal, probably not.  I have most of them but, If I don't run regions, I can crank my sliders up quite high.  If I do run regions, I have to move them back in order to keep VAS and framerate in check.  (See my specs below.)  With heavy metal I only run OpenLC, sometimes Orbx Vector, and quality airports.  Maybe when P3D64 comes out and I get a significantly stronger machine it'll be worth it.

53 minutes ago, Boomer said:

 Would it be worth the fps and vas hit?

You should look at my FSUIPC log above regarding my flight to KSAN over Orbx SoCal.  I had a high of 159 fps according to the report and had an average of 52 fps for most of the flight.  In P3D, LM manages your VAS so the amount of VAS available fluctuates up and down during a flight session.  The minimum VAS space I had during my flight was 718MB and I ended up with a little more than 1GB a little bit less than what I had started out with.  Flight was with FSDT's KLAX, Orbx SoCal and KSAN, PMDG 738 and AS16 weather (and ASCA).  One thing I do not enable in P3D that I found took up FPS and VAS is cloud shadows.  Might be good for VFR flights but not for flights with heavies.  I still have shadows in the cockpit.

Personally, I wish the people who are reporting VAS/FPS issues with Orbx scenery and/or P3D would post their FSUIPC log that has logging enabled and VAS monitoring.  I can easily bring P3D to its knees while flying over photo scenery or Orbx regions.  I have a very powerful system too but it would be easy by enabling high settings in the P3D.cfg and display driver settings (or NI). I could also probably throw in the BufferPool tweak and bring it down even faster.  My point is that in using flight simulation software and add-ons, you have to be wary of your settings.  You cannot max things out or almost max things out because you have a powerful system.  If anyone does that, then I would recommend they leave the hobby of flight simulation and found something else to keep them entertained (these comments are not meant for you but for everyone reading this).

I plan on doing a flight with the PMDG 747 from Flightbeam's KSFO to KSAN soon and will post my results then.  I have tried the flight a couple of times but it crashed near landing at KSAN.  Not because of a lack of VAS or FPS but got the G3D.dll error.  I discovered I did not have the latest version of P3D installed (the one that fixed the video card SLI issue) and that stopped my G3D.dll crashes.  Fortunately, Pete trapped this error in FSX with his fsuipc utility and you can see in the FSX log above that I was hit with a G3D error a couple of times during the flight but they were successfully trapped.

Best regards,

Jim

Hi all,

I was also on the fence between LatinVFR and the ORBX version. Initially I was also negative about ORBX but in the end decided to buy the ORBX one. I made some comparison screenshots (thought not in the same angle) using Jordan's King very nice comparison video and also Aviation Man's Google link (thanks for the link!) :

My impression based on this is :

• LatinVFR has more accurate tarmac colors. The ORBX has significantly dark tarmac color.
• LatinVFR has more accurate jetbridges, white in color. ORBX has grey ones with less textures, not like the real world.
• ORBX has better terminal modeling. If you look at the Google image the ORBX's version follows precisely the real buildings model and color (maybe darker in some cases). LatinVFR terminal models are not that accurate.
• ORBX has more precise line markings to the real world, though both don't have the exact copy of the real world airport, but you can see the difference in the screenshots.
• ORBX has better surrounding area in my opinion.

That's why I deciced to go with t he ORBX version, though it can be improved. I think if they could update the tarmac color with a more bright version, it would be even better.

By the way, I opened a topic in the ORBX support forums, suggesting in the next update to incoporate a brighter tarmac and jedbrides. In my opinion these two fixes would increase the proximity to real life exponentially :)