romoni

Well - about what ECAM tell as this problems come to active? Mayby ECAM can tell something - who knows...

TAT IN ICING RANGE Eng Ati-ice & Wings -> ON ?

Yes - I checked Yours link. You said that You have a lot payware addons. How about if You try to use only those departure / destination airports, default paint and no one extra utilies from flightsim.to? Best way to checks problems like this would be use a empty Community folder for test. I had a big problem end of the last year whit PMDG 737-800 - all button freezed but aircraft fly anyway but those problems are gone now. Reason could been Windows update or Simulator update those time or PMDG.s own update. Those all was about a same time. We have different rigs and addons. Some payware / freeware addons can cause a mysterious problem even it is other side the world. We get a lot updates from Asobo and they not go allways to right direct and caused problems to addon sceneries if they not updated, too. Empty Community folder - only departure / arrival airport / default paint and a few test flight Sorry my poor english

Testing version 1.03 Update between EDDK - LEBL and not found any problems. Works as well as before 1.02 version so about where the problems are - between chair and screen mayby...

Tested and papi of the KORS works perfectly now. Thank Yoy Christian! Rolf

Hi Christian! I'll check this - thank You for Yours info. Rolf

Ok - read Readme, Manual, How to -guide and read forums and finally installed. I have all versions of the Fixer and tryed it many times before without successed but now - today I finally got the Fixer working by using a hard brain work. I was a little bit suprised that how much better sceneries (tetsted ORBX KORS area) looked out. Yes - ofcourse - a one problem occured yet but it is KORS problem. I mean those flashing PAPI lights and I think that there is no solution for that... Anyway - thank You Steve who made this "must be"-addon. Rolf

Hi Steve! Very quick reply - thanks a lot. Yes - procedures are understood! Rolf

Hello! Couple unclear question before I try Fixer again: 1. Quate from Readme: "There are only two bitmaps of significance to DX10SceneryFixer <FSX DIR>\bkg.bmp <FSX DIR>\Texture\envmap.bmp. Currently you must restore the originals before the installation can proceed. If you do not do this then the installation will abort with a message explaining the issue." Ok - I made backup those files - should I to delete them before I start Fixer installation? 2. Could it be any harm if I have a lot addon (ORBX etc.) installed before I install Fixer? I use FSX Gold Edition (boxed). Rolf

Ok - first attempt to fly the Tutorial flight is done - not perfect but it's done anyway. All systems seems to be working now so practise will continue and hopefully those problems not come back... Rolf

Hi! Yes - installed as admin as allways. I made a new re-installation and will see what happen Rolf Ok - the situations is as yestarday after Dash re-installation. I'll check later how it works... Rolf

Hello! Windows 7 64bit Home Edition, nVidia GTX 560 OC 1G, FSX Gold Edition. I bought this addon July 3 2013 but I don't used it a lot - mayby twice but a few days ago I bought a training video (part 1-10) and reason of that I decided to start to practise this bird yestarday. I spent all day yestarday to get it works. As I started my practise session I found that buttons not works, gauges not works and displays are dark and pop up not works. Well - I tryded a few times - shut down FSX and re-start but same results. Ok - then I re-insllaed this addon - first ver. 1_008 and after that updated patch1_00801-2-3 - started FSX and shut down and re-start Windows. After that I started FSX, selected Q400 with Porter paint to check about what is situation now. Haaa... Everythings worked as they should be but it was time to do something else and I left the practise session to next day. But today all problems are back except for button - they moved as I clicked them and got APU to ON - thats all. I have a two pictures here if it cleared better my problem than my poor english... If somebody could help me I would be very thankfully. Rolf

Thanks for Info, Aviators! Rolf

There is some problem - is it down or what is going on. I can't to activate my product and I can't access to Support Portal to sent Ticket to PMDG. Has anybody to give some information? Thank You! Rolf

There is some problem - is it down or what is going on. I can't to activate my product and I can't access to Support Portal to sent Ticket to PMDG. Has anybody to give some information? Thank You! Rolf

Thank You!

Thank You - nice work! Rolf

Hi Jim! No problem at all and thank You for all Yours help now and mayby in future. I'm very happy that I found helpfully man like You! I'm testing this bird now and it's seem to be working very well now and as I get those RXP stuffs working the plane is perfect - mayby the gauge lights would be a crown to finalize a flight experiencies. Best regards Rolf PS. I stay tuned :lol:

Hi Jim! Yes - I understand. BTW - I have 337, too and the lights are perfect. About what I meen You can see it this video - timeline 1:48 Instrument lights are very soft... Rolf

Hello Jim! Thank You very, very much for Yours help! I was pretty sure that I was made some mistake during configuration of the SW Lights. Now the lights are as they should be on out side. I'm not sure (I'm not tesred it today, yet) but I remember that I have seen some pictures taken from Cockpit and there was very good looking Gauge lights but what I know the Caravan's has only one switch and it's Panel light? Panel lights is too bright during night so that why I ask if this is some solution. Ok - I understand if I want too much at one time but it would be very nice to get Caravan tuned as much as possible. I found a one solution about how to get Reality XP's working with this bird so it's will be a next step on my tuning list. This is very good forum - thank You! BTW - this is what works perfect if sonebody else found the same problem: [Lights] // types: 1=beacon, 2=strobe, 3=navigation, 4=cockpit, 5=landing, 6=Taxi, 7=Recognition, 8=Wing, 9=Logo, 10=Cabin light.0 = 3, -17.48, -26.30, 3.92, fx_shockwave_navred light.1 = 3, -17.75, 26.30, 3.92, fx_shockwave_navgre light.2 = 3, -43.87, 0.12, 1.74, fx_shockwave_navwhi light.3 = 2, -17.70, -26.30, 3.92, fx_shockwave_strobe_2 light.4 = 2, -17.97, 26.30, 3.92, fx_shockwave_strobe_3 light.5 = 1, -41.75, 0.00, 10.45, fx_beaconcardose light.6 = 9, -11.61, 0.00, 0.98, fx_vclightcardose light.7 = 10, -12.61, 0.00, 2.10, fx_vclightcardose1 light.8 = 10, -15.61, 0.00, 2.10, fx_vclightcardose1 light.9 = 10, -20.61, 0.00, 2.10, fx_vclightcardose1 light.10 = 10, -25.91, 0.00, 2.10, fx_vclightcardose1 light.11 = 10, -11.81, 0.00, 0.98, fx_vclightcardose2 light.12 = 6, -15.80, -17.55, 3.80, fx_shockwave_landing_light_small_old light.13 = 6, -15.80, 17.55, 3.80, fx_shockwave_landing_light_small_old light.14 = 5, -15.80, -17.00, 3.80, fx_shockwave_landing_light_small_old light.15 = 5, -15.80, 17.00, 3.80, fx_shockwave_landing_light_small_old gauge10=Shockwave_Lights!SW Lights, 484,497,20,12 Rolf

Well... I made a test with RealAir Duke and found the same problem. Mayby I meshed something as I tryed DX10 a few weeks ago. I made some configuration for lights because they don't work very well during night so I returned back to DX9. I must hunting my backup files if I'll find some missing textures or something else... Rolf OK - SW Lights work with Duke but no Caravan. I reloaded SW Lights and reinstalled it. I realeased that I used an older version of Shockwave Lights but, but...

Thank You! I treyd this yesterday and today but no luck. Very odd as I said before... Rolf

Here is a two shots:

Hi Jim and VeryBumpy! Thank You. I tryed to add the line to the panel.cfg but the result was that only landing/taxi lights illuminate. This is my config both Aircraft and panel.cfg: Aircraft.cfg: ... [pitot_static] vertical_speed_time_constant = 1.0 pitot_heat = 1.0 [Radios] // Radio Type = availiable, standby frequency, has glide slope Audio.1 = 1 Com.1 = 1, 1 Com.2 = 1, 1 Nav.1 = 1, 1, 1 Nav.2 = 1, 1, 1 Adf.1 = 1 Transponder.1 = 1 Marker.1 = 1 [Lights] //Types: 1=beacon, 2=strobe, 3=navigation, 4=cockpit, 5=landing, 6=Taxi, 7=Recognition, 8=Wing, 9=Logo, 10=Cabin light.0 = 3, -17.48, -26.30, 3.92, fx_shockwave_navredlight light.1 = 3, -17.75, 26.30, 3.92, fx_shockwave_navgrelight light.2 = 3, -43.87, 0.12, 1.74, fx_shockwave_navwhilight light.3 = 2, -17.70, -26.30, 3.92, fx_shockwave_strobe_2light light.4 = 2, -17.97, 26.30, 3.92, fx_shockwave_strobe_3light light.5 = 1, -41.75, 0.00, 10.45, fx_shockwave_beaconhlight light.6 = 9, -11.61, 0.00, 0.98, fx_vclightcardoselight light.7 = 10, -12.61, 0.00, 2.10, fx_vclightcardose1light light.8 = 10, -15.61, 0.00, 2.10, fx_vclightcardose1light light.9 = 10, -20.61, 0.00, 2.10, fx_vclightcardose1light light.10 = 10, -25.91, 0.00, 2.10, fx_vclightcardose1light light.11 = 10, -11.81, 0.00, 0.98, fx_vclightcardose2light light.12 = 6, -15.80, -17.55, 3.80, fx_shockwave_landing_light_smalllight light.13 = 6, -15.80, 17.55, 3.80, fx_shockwave_landing_light_smalllight light.14 = 5, -15.80, -17.00, 3.80, fx_shockwave_landing_lightlight light.15 = 5, -15.80, 17.00, 3.80, fx_shockwave_landing_lightlight light.16 = 5, -2.00, -19.00, 1.00, fx_shockwave_landing_light_light_smlight light.17 = 5, -0.50, 19.00, 1.00, fx_shockwave_landing_light_light_sm panel.cfg: ... //-------------------------------------------------------- [Window04] file=info.bmp size_mm=555,139 window_size_ratio=1.000 position=0 visible=1 ident=142 window_size= 0.290, 0.097 window_pos= 0.350, 0.020 //-------------------------------------------------------- [Vcockpit01] Background_color=0,0,0 size_mm=512,512 visible=0 pixel_size=1024,1024 texture=$Panel_CARAV_1 gauge00=GCCB!Airspeed, 2,4,164,164 gauge01=GCCB!Attitude, 170,4,164,164 gauge02=GCCB!Altimeter, 341,3,164,164 gauge03=GCCB!rmi, 1,174,165,165 gauge04=GCCB!Horizontal Situation Indicator, 169,173,168,168 gauge05=GCCB!Vertical_speed, 340,173,167,167 gauge06=GCCB!vor2, 1,343,164,164 gauge07=GCCB!Turn_Coordinator, 169,343,162,166 gauge08=GCCB!DME_screen, 333,351,176,68 gauge09=GCCB!Panel_annunciator, 333,428,175,65 gauge10=Shockwave_Lights!SW Lights, 484,497,20,12 If You need some picture before / after I'll take them. This is very odd and this is a first time as I have problem like this with Shockwave Lights. As default config the lights work very well. I have REX and AS2012 but I don't use their lights - they are unticket... Rolf

Hello! May I ask if I'm understand right this config? Here is what I have onto Aircraft.cfg: [Lights] 1=beacon, 2=strobe, 3=navigation, 4=cockpit, 5=landing, 6=Taxi, 7=Recognition, 8=Wing, 9=Logo, 10=Cabin //Types: light.0 = 3, -17.48, -26.30, 3.92, fx_shockwave_navredlight light.1 = 3, -17.75, 26.30, 3.92, fx_shockwave_navgrelight light.2 = 3, -43.87, 0.12, 1.74, fx_shockwave_navwhilight light.3 = 2, -17.70, -26.30, 3.92, fx_shockwave_strobe_2light light.4 = 2, -17.97, 26.30, 3.92, fx_shockwave_strobe_3light light.5 = 1, -41.75, 0.00, 10.45, fx_shockwave_beaconhlight light.6 = 9, -11.61, 0.00, 0.98, fx_vclightcardoselight light.7 = 10, -12.61, 0.00, 2.10, fx_vclightcardose1light light.8 = 10, -15.61, 0.00, 2.10, fx_vclightcardose1light light.9 = 10, -20.61, 0.00, 2.10, fx_vclightcardose1light light.10 = 10, -25.91, 0.00, 2.10, fx_vclightcardose1light light.11 = 10, -11.81, 0.00, 0.98, fx_vclightcardose2light light.12 = 6, -15.80, -17.55, 3.80, fx_shockwave_landing_light_smalllight light.13 = 6, -15.80, 17.55, 3.80, fx_shockwave_landing_light_smalllight light.14 = 5, -15.80, -17.00, 3.80, fx_shockwave_landing_lightlight light.15 = 5, -15.80, 17.00, 3.80, fx_shockwave_landing_lightlight light.16 = 5, -2.00, -19.00, 1.00, fx_shockwave_landing_light_light_smlight light.17 = 5, -0.50, 19.00, 1.00, fx_shockwave_landing_light_light_sm I ask because I can see only a landing lights. Should I put some line to panel.cfg under [VirtualCockpit]? Rolf