My REX Settings:

 

Is there any technical reason you don't use the sky textures from the AVSIM library anymore? I like those textures much more than the REX4 ones and just want to make sure they don't make any problems with Prepar3d v3.

Is there any technical reason you don't use the sky textures from the AVSIM library anymore?

 

The AVSIM library textures look great at dusk/dawn but as soon as any reduce visibility is introduced it starts to look odd.  Also during day time hours that sky texture seemed to produce a dark grayish cast on everything.  So in V3, I'm back to the REX sky textures.

 

Cheers, Rob.

Guess I have been lucky then as I have flown from Dubai (FT) to EGLL (Aerosoft) a few times in v3 and never had an OOM so far and yes I have FTX England as well. I used 2048 textures. I dont have all the other setting maxed out but they are in the high parts of the sliders.

I just had my very first OOM using the IFLY 747 V2 in v3. No Orbx England Or Vector. I was at Aerosoft Heathrow, about to start my engines then i got an OOM. So it's definitely the IFLY for me. Any other aircraft on high settings, im fine.

 

Wayne George

Well, at least you know what caused the OOM and you can adjust your settings accordingly when flying the iFly 747.  I know version 1a was just released for P3Dv2 users so that it is compatible in v3.

 

I personally would suspect Aerosoft Heathrow as I think that is heavy on FPS.  IFly aircraft have a lot of eye-candy too and coupled with an airport with a lot of eye-candy, that's a prescription for major issues.  Since I own the iFly737 for P3D, think I'll get the 747.  Have been looking at that for some time now.  I have my settings for P3Dv3 really low and use GEP3D/UTX instead of Orbx.  I'm enjoying my flights so far.  If I have any problems with the iFly747, I'll let you know (if I decide to buy it).

 

Best regards,

I have to agree something is eating up VAS when the iFly747 is loaded.  I just did a short takeoff/landing at FlightBeams KIAD (Wash Dulles) and it lost a lot of VAS fast.  Problem is, I cannot prove it was the iFly747.  Here's the VAS report from FSUIPC:
 

******** FSUIPC4, Version 4.946 by Pete Dowson *********
Reading options from "K:\Prepar3D v3\Modules\FSUIPC4.ini"
Running inside Prepar3D v3 on Windows 7
Module base=19CA0000
User Name=
User Addr=
FSUIPC4 Key is provided
WIDEFS7 not user registered, or expired
31 System time = 10/12/2015 18:32:40
31 FLT path = "C:\Users\JimY\Documents\Prepar3D v3 Files\"
31 Trying K:\Prepar3D v3\Modules\SimConnectP3D2.dll
31 Found it: trying to connect
31 FS path = "K:\Prepar3D v3\"
172 LogOptions=00000000 00000001
172 -------------------------------------------------------------------
172 ------ Setting the hooks and direct calls into the simulator ------
172 --- CONTROLS timer memory location obtained ok
172 --- SIM1 Frictions access gained
172 --- FS Controls Table located ok
172 --- Installed Mouse Macro hooks ok.
172 --- Wind smoothing fix is installed
172 --- All links checked okay
172 -------------------------------------------------------------------
172 SimConnect_Open succeeded: waiting to check version okay
172 Trying to use SimConnect Prepar3D
30826 Running in "Lockheed Martin® Prepar3D® v3", Version: 3.0.3.0 (SimConnect: 3.0.0.0)
30826 Initialising SimConnect data requests now
30826 FSUIPC Menu entry added
30841 C:\Users\JimY\AppData\Local\Lockheed Martin\Prepar3D v3\Prepar3D_Default.fxml
30841 K:\Prepar3D v3\SimObjects\Airplanes\IRIS Raptor Driver\Raptor.air
31637 Monitor IPC:024C (S32) = 3224184
41605 Monitor IPC:024C (S32) = 3088984
51589 Monitor IPC:024C (S32) = 3090008
61823 Monitor IPC:024C (S32) = 3089496
71807 Monitor IPC:024C (S32) = 3090520
91775 Monitor IPC:024C (S32) = 3090008
102009 Monitor IPC:024C (S32) = 3091032
121977 Monitor IPC:024C (S32) = 3090520
131961 Monitor IPC:024C (S32) = 3091032
141992 Monitor IPC:024C (S32) = 3010736
152085 Monitor IPC:024C (S32) = 3012940
162194 Monitor IPC:024C (S32) = 2970688
166827 K:\Prepar3D v3\SimObjects\Airplanes\iFly 744\iFly744_RR.air
172178 Monitor IPC:024C (S32) = 2120268
182162 Monitor IPC:024C (S32) = 1928816
192630 Monitor IPC:024C (S32) = 1763284
201132 System time = 10/12/2015 18:36:01, Simulator time = 13:35:22 (18:35Z)
201132 Aircraft="iFly 747-400 RR (Normal screen)"
202099 Starting everything now ...
202177 Monitor IPC:024C (S32) = 1364864
203378 ASN active function link set
203378 Ready for ASN WX radar
206280 Advanced Weather Interface Enabled
212208 Monitor IPC:024C (S32) = 1195124
222270 Monitor IPC:024C (S32) = 1234812
232317 Monitor IPC:024C (S32) = 1235536
252394 Monitor IPC:024C (S32) = 1224812
262425 Monitor IPC:024C (S32) = 1223788
282455 Monitor IPC:024C (S32) = 1224300
292517 Monitor IPC:024C (S32) = 1224812
302564 Monitor IPC:024C (S32) = 1225324
312610 Monitor IPC:024C (S32) = 1224812
342750 Monitor IPC:024C (S32) = 1224052
362811 Monitor IPC:024C (S32) = 1208432
372842 Monitor IPC:024C (S32) = 1184540
382889 Monitor IPC:024C (S32) = 1195552
392935 Monitor IPC:024C (S32) = 1195040
412966 Monitor IPC:024C (S32) = 1184624
432996 Monitor IPC:024C (S32) = 1184004
443012 Monitor IPC:024C (S32) = 1183492
453042 Monitor IPC:024C (S32) = 1182732
463073 Monitor IPC:024C (S32) = 1183756
473135 Monitor IPC:024C (S32) = 1183212
493228 Monitor IPC:024C (S32) = 1143780
503290 Monitor IPC:024C (S32) = 1167020
513337 Monitor IPC:024C (S32) = 1166248
533461 Monitor IPC:024C (S32) = 1133656
543507 Monitor IPC:024C (S32) = 1162220
563522 Monitor IPC:024C (S32) = 1161708
583600 Monitor IPC:024C (S32) = 1160164
593677 Monitor IPC:024C (S32) = 1160088
603677 Monitor IPC:024C (S32) = 1158800
613724 Monitor IPC:024C (S32) = 1143124
623754 Monitor IPC:024C (S32) = 1133360
633770 Monitor IPC:024C (S32) = 1129728
643847 Monitor IPC:024C (S32) = 1132272
653894 Monitor IPC:024C (S32) = 1122544
663925 Monitor IPC:024C (S32) = 1129196
673955 Monitor IPC:024C (S32) = 1126248
683986 Monitor IPC:024C (S32) = 1124072
694002 Monitor IPC:024C (S32) = 1129636
704064 Monitor IPC:024C (S32) = 1124432
714063 Monitor IPC:024C (S32) = 1099152
724125 Monitor IPC:024C (S32) = 1121008
734156 Monitor IPC:024C (S32) = 1123048
744187 Monitor IPC:024C (S32) = 1123920
754234 Monitor IPC:024C (S32) = 1126128
764264 Monitor IPC:024C (S32) = 1119044
774327 Monitor IPC:024C (S32) = 1120984
784342 Monitor IPC:024C (S32) = 1122020
794357 Monitor IPC:024C (S32) = 1122024
804419 Monitor IPC:024C (S32) = 1120996
814419 Monitor IPC:024C (S32) = 1042936
824450 Monitor IPC:024C (S32) = 1119956
834527 Monitor IPC:024C (S32) = 1120984
844558 Monitor IPC:024C (S32) = 1126364
854558 Monitor IPC:024C (S32) = 1129760
864651 Monitor IPC:024C (S32) = 1120848
874666 Monitor IPC:024C (S32) = 1159312
884697 Monitor IPC:024C (S32) = 1169424
894775 Monitor IPC:024C (S32) = 1168396
904853 Monitor IPC:024C (S32) = 1174852
914899 Monitor IPC:024C (S32) = 1170452
924914 Monitor IPC:024C (S32) = 1010088
934914 Monitor IPC:024C (S32) = 1122188
944976 Monitor IPC:024C (S32) = 1122756
955022 Monitor IPC:024C (S32) = 1106504
965069 Monitor IPC:024C (S32) = 1094436
975084 Monitor IPC:024C (S32) = 1094736
985131 Monitor IPC:024C (S32) = 1101224
995193 Monitor IPC:024C (S32) = 1096104
1005255 Monitor IPC:024C (S32) = 1019704
1015270 Monitor IPC:024C (S32) = 1083516
1025301 Monitor IPC:024C (S32) = 1084028
1045378 Monitor IPC:024C (S32) = 1086580
1055394 Monitor IPC:024C (S32) = 1087100
1065424 Monitor IPC:024C (S32) = 1083004
1075502 Monitor IPC:024C (S32) = 1088636
1085533 Monitor IPC:024C (S32) = 1083516
1095548 Monitor IPC:024C (S32) = 1067324
1105595 Monitor IPC:024C (S32) = 1065780
1115657 Monitor IPC:024C (S32) = 1072448
1125703 Monitor IPC:024C (S32) = 1061836
1135765 Monitor IPC:024C (S32) = 1056412
1145796 Monitor IPC:024C (S32) = 1057956
1165920 Monitor IPC:024C (S32) = 1057440
1171786 Sim stopped: average frame rate for last 971 secs = 17.3 fps
1175936 Monitor IPC:024C (S32) = 1129868
1185951 Monitor IPC:024C (S32) = 1050420
1195997 Monitor IPC:024C (S32) = 1051956
1206059 Monitor IPC:024C (S32) = 1051444
1216106 Monitor IPC:024C (S32) = 1034224
1226121 Monitor IPC:024C (S32) = 1037884
1229023 Sim stopped: average frame rate for last 52 secs = 16.5 fps
1243765 === NOTE: not calling SimConnect_Close ...
1244763 System time = 10/12/2015 18:53:24, Simulator time = 13:52:20 (18:52Z)
1244763 *** FSUIPC log file being closed
Minimum frame rate was 11.2 fps, Maximum was 29.9 fps
Minimum available memory recorded was 986Mb
Average frame rate for running time of 1023 secs = 17.3 fps
Memory managed: 233 Allocs, 233 Freed
********* FSUIPC Log file closed ***********

 

 

Best regards,

I had an OOM with P3Dv3 and the PMDG 777-300 on a flight from Toronto to London. Fortunately it crashed after I was on the ground at Heathrow and taxiing to the gate. 

I had an OOM with P3Dv3 and the PMDG 777-300 on a flight from Toronto to London. Fortunately it crashed after I was on the ground at Heathrow and taxiing to the gate. 

Are you using Orbx England & Orbx Vector? If so those are whats causing the OOMS. If i don't have those two running, i am absolutely fine

I am running ORBX Vector.

Why using ORBX region when flying heavy aircraft that fly at least 34000 ft above the ground? I only use ORBX when flying low with small aircraft.

I don't think that 64 bit is going to happen for P3d.

What is complex about implementing 64-bit? Is it more than using a modern compiler?

 

 

What is complex about implementing 64-bit? Is it more than using a modern compiler?

 

Yes it's more ... biggest drawback is that it will break compatibility with many existing 3rd party products.

 

As for 64bit P3D, I "think" it will happen, just not a V3.x series.  There are A LOT of other changes to the SDK that would need to happen also including "possible" conversion tools.  But as we've seen from DTG, some sceneries provided by Orbx seem to be able to work well in a 64bit DTG ... so some elements of 64bit will require less work than other elements.

 

Cheers, Rob.

Yes it's more ... biggest drawback is that it will break compatibility with many existing 3rd party products.

 

As for 64bit P3D, I "think" it will happen, just not a V3.x series.  There are A LOT of other changes to the SDK that would need to happen also including "possible" conversion tools.  But as we've seen from DTG, some sceneries provided by Orbx seem to be able to work well in a 64bit DTG ... so some elements of 64bit will require less work than other elements.

 

Cheers, Rob.

 

That's interesting, I hope LM is working in this direction already.

Microsoft Flight Simulator transitioned from 16 to 32-bit, anyone remember when? Was it FS 5.1 (DOS) to FS For Windows95? I remember having to use some converters regarding aircraft only, but my memory is really not much good on this.

Thanks!

The best thing to do is turn off all....ALL scenery of lower United Kingdom....UK2000 and Orbx alike.  I suffered ill-ingly for hours struggling to get out of Heathrow in either UK2000 or AS_LHR Extended.  I was only able to achieve success when deactivating those scenery like Southampton and UK2000 EGKK/EGLC