StephanS

Still no news about a work in progress SP2 or any developer regarding this issue ??sad...(maybe we have to post it in the 737ngx forum :( )

Thanks to the PMDG-Team for ongoing improvemenst and support !Possibly there may be some time for an update for the JS41-flickering texture issue :( ( http://forum.avsim.net/topic/278682-texture-flickering-flashing/ )And by the way, I also use FSrealWX with success...

Have to revert this issue: Today everything is working fine with the flood-light.Maybe there was anything in memory as I tested yesterday.Please disregard this one...

Hello,on a flight yesterday in dusk I`ve noticed, that the honeywell-mcp stays dark with the mcp flood-lights turned on.Only the knobs and switches reflected the light.Switching to the Collins-MCP shows that the collins mcp reflects the flood lights well in dusk/dawn.Further with the sim at night also the honeywell mcp were lightened up as it should be ...Maybe it is only a meterial-definition in the modell or a channel-issue in one of the textures...Not an important thing but I hope it can be fixed...Maybe anyone can reproduce...(I don`t mean the knobs/display lighting which is turned on with the "Panel-Light" switch, this is working well. I mean the MCP-Flood-light (switch below Navigation-Display)Thanks & Regards,Stephan

Very nice one.Here comes another PIC of it...

I have a diffenrece of 4-6 frames when loading the JS-41 before.As my System is not actual (E8500 dualcore , nvidia-9800 with 512MB). But this effect is not mesurable when directly loading the NGX.I have to look around (with Track-IR) until all Textures from the surrounding scenery and the cockpit are loaded. When FSX finally runs a while, I can compare both situations (with preloading JS-41 and without...). For this test I have used the same FSX.CFG and the same situation/weather-condition. What I did not: I have not testetd or compared yet, if this increasement of frames is stable along a whole flight of 1-2 hours.

Tried it in LSZA without any third party tool and it was working fine. Then I tuned the temperature manually inside FSX and when fsx exaclty hits the 15°C and the present aircraft altitude it seems to malfunction.In addition the application crashes, when I try to uncheck the checkbox "Auto Get Data"I can restart and away from 15°C it is working again.Hope this helps.And yes : thank you again. Rock on, this is a great tool ! :(

Yes: it happened at an online-flight with active-sky and sqwakbox (running on a remote PC). I will try it without the other tools...Regards,Stephan

I `ve had an Error when I positioned at Lugano LSZA (Switzerland):The Tool says, that it is unable to calculate. The fields in the gui went red: "temperature=15" and the "elevation=915" (i guess).When I tried to disable the automatic data reading from fsx the tool crashes.Regards Stephan

Thank you for this great enhancement and for sharing this with us.I also like to run the app on a remote pc, but when I start it on the remote pc, it stops with an error.Other simconnect-instances are working well (f.e. plan-g, squawkbox, ...). Will it be possible to run itremote in future ?Thanks & Regards,Stephan

I don`t think that there will be a patch. This issue is very old ...Those who did not have the flickering are the lucky winners. :(

It has been a long time without an update for this problem.Any news or plans to fix this ?still flying wihtout icing-effects Regards,Stephan

No news about this topic since one month ?I would like to offer my help for testing etc. Please let me know ...

Hi Folks,sadly I have also the problem of the artifacts appearing in the VC, not everytime but often !As my System is not one of the high end range (Core2Duo E8500 , Nvidia 9800GT) I cannot believeit is any kind of "overload" (comparing other affected users and their high-end-computers here).It may be a hint, but all grafic-errors suggestet with these artifacts seems to be related to the center of the screen.Any artifact has a symetry to either the middle of the monitor-x-axis or the center-pixel (x- and y-axis).But hopefuly I saw, that PMDG is aware of the problem and has an idea of the cause. I really love the ice-effectsand I'm always racing against the warning panel by cheking the wings visauly for Icing...Let me know, if I can help in anyway to solve this.PMDG: this is still your best productRegards,Stephan Siebertz

Hi,maybe a feature-request or a request for help on the following issue:I`ve heard that with other PMDG-Addons switching the transponder gauge mode toactive (TA) initiates the Squawkbox into "mode C"Same for the way back to "Standby".The JS41 did not ! Is there any chance on realising this feature for thihs fabulous aircraft ?Or does anyone have a Gauge just for toggeling the status of transponder mode of SB in FSX.(it possibly may be a switch as a gauge that I can build in..., otherwise the solution mentionedabove should be the best !)Thanks...

Sorry, Adam. I did not mentioned: yes I have build it into the "Low-Res-Panel" (you may have to configure it firstwith the config manager and after that make the changes for the ACARS).If you want to build it in the HiRes-Version, you have to change the code shown for "VC SECTION 2" as Mitchell wrote.Mitchell, thank you for the hint. Maybe you can post the entire code you meant with "doubled numbers" here.Thanks

Ok, here we go.... IMPORTANT: the PMDG-configmanager may overwrite your changes in the panel.cfg .I don`t have tested it, but i suggest to keep this instructions in a save place to reinstall the ACARS after anupdate or a change in the panelsettings via the configmanager.!!! You should know what you are doing, use these instructions on your own risk !!! 1. Backup !! Make a backup copy of your panel.cfg !! 2. Edit the panel.cfg as follow: 2a ) Add a new line in the section [Window Titles] for your 2D-ACARS-popup-panel. Then, th section shouldlook like this: [Window Titles]Window00=GPSWindow01=Ramp ManagerWindow02=FMSWindow03=FSFK ACARS Device 2b ) Add the above mentioned new [Window03] . This is done by adding the following section behind the section of [Window02] : //--------------------------------------------------------[Window03]Background_color=0,0,0size_mm=127,95window_size_ratio=0.500 position=8visible=0ident=15372 gauge00=FSFK-ACARS!Device, 0,0,127,95 //----------------------------------------------------- 2c ) Last thing is to add the ACARS-Gauge and the clickspot into the Weather-Radar-Screen. You have to find the VC Section 2 andchange the section to the following (I re-arranged the order to ensure functionality of the main gauges): ///////////////////////////////////////////////////////// VC SECTION 2///////////////////////////////////////////////////////[VCockpit02]size_mm=512,512pixel_size=512,512texture=$GaugeTwobackground_color=0,0,0 gauge00=FSFK-ACARS!Device, 225,250,320,295gauge01=FSFK-ACARS!Hotspot, 253,250,30,30gauge02=j41!pmdg_j41_rmu_1, 0, 0, 197, 250gauge03=j41!pmdg_j41_rmu_2, 197, 0, 197, 250gauge04=PMDG_BAe_JS4100_3!GNSXLS, 1, 254, 256, 204gauge05=j41!pmdg_j41_alt_pic, 448, 0, 64, 254gauge06=j41!pmdg_j41fms_pu_open, 460,229,27,17 Have fun...

Unfortunately I have no weather-radar-addon and there is no weather-radar delivered with the JS41.So I made a compromise and build in the ACARS-Gauge from FS Flightkeeper. There area couple of benefits that comes along with that.For example you have a map while taxiing, or you can show actual weather conditions, refreshed continously...The way I choose was to build in only the ACARS-screen into the weather-radar in VC, adding a clickspotfor the 2D-Popup Full version of the ACARS. Even the nightcolor matches well.But this modification is surely a matter of taste.If PMDG allows me, I can give an instruction for modifying the panel.cfg .Here some example-screens of what I mean ...The clickspot opens a 2D-subpanel for configuring FSFK-Acars and switching the display modesThe Map-View...One of the weather pages (scrollable screen)

Hi,looks great ! I think your additions are great enhancements. I use TrackIR and have had problems reading the speedcards, even, when leaning forward.But with this change (mainly the InitialZoom ) it works better.But another question here to the PMDG-Staff:Is it allowed to post changes of the panel.cfg as well ?Unfortunately I have no weather radar-addon, but I use FS-Flightkeeper for online-flights, etc.So I worked out a solution using the FS-Flightkeeper-Screen instead of the Weather-Radar.I build in the FSFK-Gauge asa ) Screen of FSFK is seen in the screen of the weather-radar in VCb ) Clickspot top-left of the weather-radar-screen to open FSFK-Gauge as a 2D-Popupc ) 2D-Window for the FSFK-Gauge (so you can press all keys and configure the FSFK-Gauge)As FSFK can also show weather-information I found it was a good solution and it does match thecockpit layout.If your answer ist positive (I will not post the panel.cfg, only my changes & screens ) I can post it here in another thread later.

Thanks Ernie for the update here :(

Addition: It is enough to put out the SIDSTAR-Files of the Airports you will choose in the FMS.So you have to get the Transitions in manually.The Problem still exists and seems to come up, when the FMS want to access the SIDSTAR-File ofairport you typed in - either departure or destination.When I put out the departure SIDSTAR-file, the I will be successfully until entering the destination onmanual planning.When you load a plan like in the tutorial it is the same thing. The FSX freezes when the FMS seems toaccess the first SIDSTAR-Files.Doing some more testing these days if possible. Maybe anything with Vista itself :(

I have done a little bit more testing:For FSX not to freeze when making inputs into the fms you have to move away all the SIDSTARS-Files out of their folder ( ..FSX\PMDG\SIDSTARS )I have left only 2 sidstar-files (the ones relevant for the tutorial) there and FSX freezesThis means, it is not a matter of the number of files. In my case the FMS does not like any SIDSTARS-files present. Same thing with another Cycle, btw.What about the other ones here, which have the freeze-problem ?Can anyone confirm, that moving away the SIDSTARS-files will keep FSX running ? Please...Maybe a workaround until fixed, if you ask ATC for vectorized approach and departure :(

Hello,Congratulations to the JS41 ! Great product & great support here ! Looking forward to SP1...I know, this is not a wishlist here, but if you consider in any improvement later on the JS41,I would like to suggest the possibility to change the units to KG (Kilogramm) - only if this isrealistic ...I know, this would be a big change, since the load-sheet is not the only one affected (fms, gauges ...)Just a suggestion

Hi Ernie, hi Folks,First, I `m glad to see that is you, Ernie who worked for this great addon.A big thing and a thumb-up for the entire team. :( But I also have the same problemas described here: My FSX freezes when I am working with the FMS.Exactly at the moment, when I typed in KHPN (the Airport ID) for manually programming the flightplan and I should type twice ENTER (Tutorial, Page 42), I can press ENTER once and I see the FIX-Details for KHPN.This is the last thing, my FSX shows. I can switch to other applications and switch back to FSX,but nothing more happens. It is a freeze, not a CDT. The Task is still running and visible as running in the taskmanager.Some more details here:- I use Vista32-bit with FSX SP2- I`ve installed the JS41 twice- I`ve removed the flightplan (same issue when loading the plan as described above)- It happens in windowed and fullscreen mode- I use the FMS in the VC (not the 2D-popup)- When I use the Task manager to interrupt or quit FSX at this time, the details at the windows-popup (the which one, where you can choose: 1) Terminate Program , 2) Wait for response , ...) tells me, that FSX is waiting for the "csrss.exe" . But this may be an effect of trying to kill FSX via the Taskmanager, I don`t know...As I`m summarizing here, I`ve made another test:For me it seemed, that the fms is extreme busy with something. So I decided to examine the PMDG-Navdata.I then tested to move the navdata + the SIDSTAR out of their folders and as expected: IT WORKED ! ThenI`ve moved only the navdata back and i was able to type in manually a flightplan. When i finally put the>3000 SIDSTAR-files back to their origin, the freeze is back again.Conclusion: it must be something with the amount of SIDSTAR-files or similar .... may be it is a hint for you.Strange, that this is only happening on some PCs, but what is not strange today ?!And i was afraid, that the PMDG-FMS collided with the ISG-Simavionics :( :(

Perhaps nobody home ?!I made a gauge based on dsd_xml_sound for the spoilers to generate a wind sound, when they are used. I activate the sound-loop by mouseclick and change the volume in a section as shown above (3 posts back).I made another gauge wich generate a wind-sound of the lowered undercarriage. It works also with the sound-loop-activation by a mouseclick and the volume-setting in a section.My problem: when i install both gauges in a panel. one of them does not work, although i set the volume to the specific sound. I tried to combine both gauges in one, but the same problem persists.Most times it is the spoiler-sound that don`t work, and it semms to be important wich gauge you enable first by mouseclick.Please, who can give me a hint to the detail, what went wrong ?Do i have this right, that i have the possibility with dsd-xml-sound to play simultaneous sounds with different trigger-conditions and different volumes ? I thought this is contained in the manual.Here`s my dsd-ini-file:=======================[Config]MaxSounds=4ErrorFlag=0ResetVolumeVar=1 //i also tried 0 but didn`t help !LvarStop=soundstopVolumeVar=dsd_xml_sound_volume[LVars]Lvar00=DSD_XML_SOUND_ID00Lvar01=DSD_XML_SOUND_ID01[sounds]Sound00=./Sound/dsd/gearair.wavSound01=./Sound/dsd/spoilerair.wavHere`s the second gauge i programmed in addition to the spoilerwindsound above - they don`t work togehter :================================================================Gear-Wind-Sound ON/OFF(G:Var1) ! (>G:Var1) (G:Var1) 0 == if{ 0 (>L:DSD_XML_SOUND_ID00, number) } els{ 2 (>L:DSD_XML_SOUND_ID00, number) }(G:Var1)(A:AIRSPEED INDICATED, knots) s0 0 50 l0 rng if{ (A:AIRSPEED INDICATED, knots) } 50 60 l0 rng if{ 81 } 60 70 l0 rng if{ 82 } 70 80 l0 rng if{ 83 } 80 90 l0 rng if{ 84 } 90 100 l0 rng if{ 85 } 100 110 l0 rng if{ 86 } 110 120 l0 rng if{ 87 } 120 130 l0 rng if{ 88 } 130 140 l0 rng if{ 89 } 140 150 l0 rng if{ 90 } 150 160 l0 rng if{ 91 } 160 170 l0 rng if{ 92 } 170 180 l0 rng if{ 93 } 180 190 l0 rng if{ 95 } 190 200 l0 rng if{ 95 } 200 210 l0 rng if{ 96 } 210 220 l0 rng if{ 96 } 220 230 l0 rng if{ 96 } 230 240 l0 rng if{ 97 } 240 999 l0 rng if{ 98 }(>G:Var2)(A:GEAR CENTER POSITION, percent) 0 == if{ 0 (>L:dsd_xml_sound_volume, enum) } els{ (A:GEAR CENTER POSITION, percent) 4 * 20 / 80 + 100 / (G:Var2) * (>L:dsd_xml_sound_volume, enum) } 3 (>L:DSD_XML_SOUND_ID00, number)Thank you...Hopefully