Skip to content
View in the app

A better way to browse. Learn more.

The AVSIM Community

A full-screen app on your home screen with push notifications, badges and more.

To install this app on iOS and iPadOS
  1. Tap the Share icon in Safari
  2. Scroll the menu and tap Add to Home Screen.
  3. Tap Add in the top-right corner.
To install this app on Android
  1. Tap the 3-dot menu (⋮) in the top-right corner of the browser.
  2. Tap Add to Home screen or Install app.
  3. Confirm by tapping Install.

Mischa

Members
  • Joined

  • Last visited

Everything posted by Mischa

  1. Do you have forgotten to remove the gear pins?
  2. I have 3 monitors connected to 2 GTX580 in surround mode on a W7 64bit. No problem , no drops in framerates Do you have expanded you taskbar over all 3 monitors or is it fixed to only the center one? .
  3. I run dual 580s at 5760x1080 at fixed 26 FPS since V2.2 and I didn't have any issue running SLI/surround...
  4. Rob, I'm running an I7 990X with 2 GTX580 in surround mode (5900x1080) which also enables SLI. I use this configuratione since P3D 2.2and I have not seen any of the issues you describe. Both cards are working stable and in parallel wether I open a menu or anything else. Maybe it's only an issue with the more modern cards like 9xx?! Regards, Michael
  5. +1 Do a fresh install yesterday with all sceneries and new ASN and today FTX Global - that's perfect timing....
  6. Using 3x27" at 5760x1080 with 2 GTX580, SLI in surround mode. Sometimes I miss the resolution of my 30" LP3065 but the triple screens together with TrackIr are the best for the immersion of sitting within the plane.
  7. In the meantime until there is a new update from LM I have found following solution for my installation : Rex4 textures 512 32bit ASN max cloud layers 3 TEXTURE_BANDWIDTH_MULT=120 Flying over UK from London to Edinburgh today gives me stable 28-32 frames although the south was nearly overcast. Without TBM change I only got 12-16 FPS. The flight was done using the Razbam Metro, ORBX ENG and SCO and ASN actual weather (20:00z). P3D setting frames unlimited, sync and triple buffer on.
  8. I also have the problem with the GTN and the autopilot. There is no funktionality /no buttton can be pressed as long as the GTN is installed. It seems that the XML autopilot gauge stopped working. The same issue happens to the DME. No light and no function. Switching to the freeradio panel everything works as it should.
  9. Bill, thanks for your support. I have reinstalled the addon with the new installer and everything runs perfect. Flying now with the GTN is a complete new experience. The small disadvantage is that running both devices costs me about 10 FPS but that may be caused by my older I7 990X CPU so that's something I can change with next board and CPU. Thanks, Michael
  10. I have installed the addon with administrator rights several times but something went wrong with this installer. 1. I have both folders for panel configurations : panel.GTN650x2 + panel.GTN750 2. There is only one model folder model.GTN750 but no model.GTN650x2 3. I have both GTNs as popup but no GTN in the VC (switched to both stacks) Addon installer is MilViz_B55_F1GTN_v1.140806.exe Here is the panel.cfg of the panel.GTN750 folder : // This Panel.cfg file created by FS Panel Studio panel editor utility - http://www.fspanelstudio.com // Built Thursday, June 05, 2014 at 14:24 FSPS Build:22767 [Window Titles] Window00=B55 Preflight Window01=GPS Window02=Flight1 Garmin GTN750 U1 - DO NOT MODIFY Window03=Flight1 Garmin GTN650 U1 - DO NOT MODIFY [VIEWS] VIEW_FORWARD_WINDOWS=MAIN_PANEL,THROTTLE_PANEL,GPS_PANEL VIEW_FORWARD_DIR=10.000, 0.000, 0.000 //-------------------------------------------------------- [Window00] Background_color=0,0,0 size_mm=500,243 window_size_ratio=1.000 position=0 visible=0 ident=70 window_size= 0.400, 0.324 window_pos= 0.000, 0.040 gauge00=B55_XMLGauges!B55_Preflight, 0,0,500,243 //-------------------------------------------------------- [Window01] Background_color=0,0,0 size_mm=640,640 window_size_ratio=1.000 position=2 visible=0 ident=GPS_PANEL window_size= 0.355, 0.522 window_pos= 0.000, 0.030 gauge00=B55_XMLGauges!FBS_KAP140, 0,469,640,163 gauge01=B55_XMLGauges!FBS_GNS530_1d, 0,0,640,468 //-------------------------------------------------------- [Window02] Background_color=0,0,0 size_mm=937,887 position=7 visible=1 ident=14401 window_size= 0.340, 0.580 window_pos= 0.660, 0.160 zorder=99 gauge00=F1GTN!GTN750, 0,0,937,887,UNIT1.POP //-------------------------------------------------------- [Window03] Background_color=0,0,0 size_mm=937,390 position=7 visible=1 ident=14403 window_size= 0.340, 0.260 window_pos= 0.660, 0.740 zorder=99 gauge00=F1GTN!GTN650, 0,0,937,390,UNIT1.POP //-------------------------------------------------------- [Vcockpit01] file=C310_VC_01.bmp size_mm=1024,1024 visible=0 pixel_size=1024,1024 texture=$C310_VC_01 gauge00=Milviz_Sound!FBGS_XMLSound, 0,0,1,1,SimObjects\\Airplanes\\Beech_Baron_B55 Milviz\\panel\\B55 XML SND#22 gauge01=B55_XMLGauges!FBS_GNS430_2, 0,367,640,262 gauge02=B55_XMLGauges!FBS_KAP140, 0,767,640,163 gauge03=B55_XMLGauges!FBS_KR 87 ADF, 0,630,640,134 gauge04=B55_XMLGauges!B55_DME, 649,32,300,150 gauge05=B55_XMLGauges!B55_Preflight, 0,0,1,1 //-------------------------------------------------------- [Vcockpit02] file=C310_VC_02.bmp size_mm=512,512 visible=0 pixel_size=1024,1024 texture=$C310_VC_02 gauge00=B55_XMLGauges!FBS_GTX330, 0,376,512,136 gauge01=B55_XMLGauges!FBS_GNS530_1, 0,0,512,374 //-------------------------------------------------------- [Vcockpit03] file=C310_VC_01_FR.bmp size_mm=1024,1024 visible=0 pixel_size=1024,1024 texture=$C310_VC_05 gauge00=B55_XMLGauges!FBS_GNS430_2d, 0,707,640,262 gauge01=Milviz_Sound!FBGS_XMLSound, 0,0,1,1,SimObjects\\Airplanes\\Beech_Baron_B55 Milviz\\panel\\B55 XML SND#22 gauge02=B55_XMLGauges!BK_AudioPanel, 0,0,640,128 gauge03=B55_XMLGauges!FBS_GNS530_1d, 0,103,640,468 gauge04=B55_XMLGauges!FBS_GTX330, 0,571,640,136 //-------------------------------------------------------- [Vcockpit04] file=C310_VC_02_FR.bmp size_mm=512,512 visible=0 pixel_size=1024,1024 texture=$C310_VC_06 gauge00=B55_XMLGauges!FBS_KAP140, 0,106,512,131 gauge01=B55_XMLGauges!FBS_KR 87 ADF, 0,0,512,106 //-------------------------------------------------------- [Vcockpit05] Background_color=0,0,0 size_mm=1024,1024 visible=1 pixel_size=1024,1024 texture=$GTN750 gauge00=F1GTN!GTN750VC, 0,0,677,794,UNIT1 //-------------------------------------------------------- [Vcockpit06] Background_color=0,0,0 size_mm=1024,512 visible=1 pixel_size=1024,512 texture=$GTN650 gauge00=F1GTN!GTN650VC, 0,0,677,297,UNIT1 Day=255,255,255 Night=85,85,85 Luminous=140,140,140 [Default View] X=0 Y=0 SIZE_X=8192 SIZE_Y=3384 ============================== Any idea what the issue is? Thanks in advance Michael
  11. You will loose no functionality, as it is just a replacement of the the older soundgauge with an actual one.
  12. Sorry, forget to post the link to the homepage of Doug. Here is the LINK
  13. You don't need to use EMT to get full sounds for both aircrafts. See my short explanation here : LINK
  14. A lot of people miss the full extended sounds in P3D for both aircrafts. To get all these sounds back for the Legacy and Duke V2 you only have to replace the sound gauge for both planes. I don't use any migration tool. Here are the steps to get them back fully working : 1. Install the Duke and the Legacy 2. Download the dsd_fsx_xml_sound_v520 archive from Doug Dawsons's homepage 3. Unzip the archive into a temporary directory 4. Make backups from RASDuke_Sound.gau and RASLegacy_Sound.gau in your gauges directory 5. Copy the dsd_fsx_xml_sound.gau from the temporary folder into the gauges directory and rename it to RASDuke_Sound.gau 6. Copy the dsd_fsx_xml_sound.gau from the temporary folder into the gauges directory and rename it to RASLegacy_Sound.gau 7. Start P3D and enjoy both airplanes.... I have tested it in P3D v2.3 and it works perfect.
  15. Rob, try to start with a copy of the BIOSHOCK 2 profile as the base. I have tried several different profiles and also with a default profile but the Bioshock profiles gives me the best results. My problem is that with SLI enabled I cannot overclock my graphic cards, I always get an G3D.dll error. With the default settings everything is fine and I can push them to 99% without any problem. Maybe that we need a more optimzed code from LM so that this could also be improved. I only have 2 GTX580 but with v2.3 I always get my 40-50 FPS (no clouds) at 5760x1080. Cheers, Michael
  16. I have a 4 core CPU (I7 975EE - no HT) and I'm using AM=14. After several flights I have found that best performance will be achieved with : systemThreadsCPUMask=1 graphicsThreadCPUMask=12 So Q400 systems are running on "unused" CPU 1 (which is used for ASN etc.) and the graphics are running on core 3 and 4. Setting both tasks to CPU 1 gives me more stuttering espacially if flying over more detailed landscape (e.g. ORBX areas). All tests were done with FTX Global / Vector / ASN and UT2.
  17. I see a great difference for Milviz B737 and QW 757 - both ACs no longer eat up the VAS memory ! Well done !
  18. UT2 is running fine without any problem in P3D V2. The ACs do not produce any shadow but that isn't an issue of P3D.
  19. I run P3D with 2 GTX580 in surround mode (5760*1080). I have the most sliders in the "normal" position, no internal shadows and have stable (internal fixed) 30 FPS. In some areas it dropps to 25-26 but I have to look at the FPS counter to realize it. P3D runs very smooth also with less FPS. No idea what this would mean in 3D.
  20. Matt, try FIBER_FRAME_TIME_FRACTION=0.1 and BUFFERPOOLS=0 in the CFG file. This made my P3D smooth without any stutter. Regards, Michael
  21. I have installed complete AU with all airports according the way Jerome has mentioned and the result is perfect! AU is the first part of the ORBX regional sceneries with the new lightning and it is breathtaking. Cheers, Michael
  22. I have set the FFTF to a value of 0.1 and Bufferpools to 0 which has eliminated any stutter. Cheers, Michael
  23. Guenter, I also have two GTX580 3GB and facing the same issue. The load can only be reduced if you force your FPS to a value to 25 or less. Any value above will give my cards a workload of 99% with or without SLI enabled. But the 99% don't have any impact to the smoothness so I'm fine with this. Cheers, Michael
  24. Regarding FSE you have to do nothing, just start the client after P3D is up and everything is fine. I have made several flights due the last days without any problems. Cheers, Michael

Account

Navigation

Search

Search

Configure browser push notifications

Chrome (Android)
  1. Tap the lock icon next to the address bar.
  2. Tap Permissions → Notifications.
  3. Adjust your preference.
Chrome (Desktop)
  1. Click the padlock icon in the address bar.
  2. Select Site settings.
  3. Find Notifications and adjust your preference.