Jump to content

jahurz

Members
  • Content Count

    28
  • Donations

    $0.00 
  • Joined

  • Last visited

Community Reputation

9 Neutral

Profile Information

  • Gender
    Male

Flight Sim Profile

  • Commercial Member
    No
  • Online Flight Organization Membership
    none
  • Virtual Airlines
    No

About Me

  • About Me
    Casual FlightSimmer and also planespotter do visit my Jetphotos or Airliners.net to check it out
    https://www.jetphotos.com/showphotos.php?userid=62725
    https://www.airliners.net/search?user=162691

Recent Profile Visitors

The recent visitors block is disabled and is not being shown to other users.

  1. Dug up this old dinosaur and reinstalled it to my flight sim and still no Altitude callout on approach. Decided to dig around and found a Temporary workaround. Steps 1) Download Boeing_Callouts_fsx.zip from flightsim or avsimLibrary. 2) unzip the downloaded zip file and place CALLOUT_SmallJets.CAB to gauge folder. Note ignore CALLOUT_SOUND.dll as this dll is no longer compatible with p3dv4 onwards. 3) also place the entire Sound folder into the root directory of gauge folder as well. It should look like gauges\Sound\Callout. Inside Callout folder is where all the GPWS altitude callouts in audio wav file and the Sound.ini config is at. 4) Download dsd_p3d_xml_sound_x64 from https://www.douglassdawson.ca/dsd_p3d_xml_sound_x64.zip 5) unzip the file and move dsd_p3d_xml_sound_x64.dll and dsd_fsx_xml_sound.ini to gauges folder. You should have dsd_p3d_xml_sound_x64.dll and dsd_fsx_xml_sound.ini at the gauges folder. 6)Rename dsd_fsx_xml_sound.ini to dsd_p3d_xml_sound_x64.ini 5) Next head to SimObjects\Airplanes\Carenado F50\panel open Panel.cfg 6)Add the following line under [Vcockpit01] gaugexx=dsd_p3d_xml_sound_x64!Sound, 0,0,0,0, Sound\CALLOUT\Sound.ini gaugexx=CALLOUT_SmallJets!CALLOUT2500, 0,0,0,0 gaugexx=CALLOUT_SmallJets!CALLOUT1000, 0,0,0,0 gaugexx=CALLOUT_SmallJets!CALLOUT500, 0,0,0,0 gaugexx=CALLOUT_SmallJets!CALLOUT100, 0,0,0,0 gaugexx=CALLOUT_SmallJets!CALLOUT50, 0,0,0,0 gaugexx=CALLOUT_SmallJets!CALLOUT40, 0,0,0,0 gaugexx=CALLOUT_SmallJets!CALLOUT30, 0,0,0,0 gaugexx=CALLOUT_SmallJets!CALLOUT20, 0,0,0,0 gaugexx=CALLOUT_SmallJets!CALLOUT10, 0,0,0,0 gaugexx=CALLOUT_SmallJets!CALLOUTMIN, 0,0,0,0 gaugexx=CALLOUT_SmallJets!CALLOUTAPPMIN, 0,0,0,0 Remember to amend gaugexx based on subsequent sequence. for e,g my previous gaugexx is gauge06=GAUGEF50!Gauge_VSI_DIGITAL, 609,0, 320,320 so my entire next line would be gauge07=dsd_p3d_xml_sound_x64!Sound, 0,0,0,0, Sound\CALLOUT\Sound.ini gauge08=CALLOUT_SmallJets!CALLOUT2500, 0,0,0,0 gauge09=CALLOUT_SmallJets!CALLOUT1000, 0,0,0,0 gauge10=CALLOUT_SmallJets!CALLOUT500, 0,0,0,0 gauge11=CALLOUT_SmallJets!CALLOUT100, 0,0,0,0 gauge12=CALLOUT_SmallJets!CALLOUT50, 0,0,0,0 gauge13=CALLOUT_SmallJets!CALLOUT40, 0,0,0,0 gauge14=CALLOUT_SmallJets!CALLOUT30, 0,0,0,0 gauge15=CALLOUT_SmallJets!CALLOUT20, 0,0,0,0 gauge16=CALLOUT_SmallJets!CALLOUT10, 0,0,0,0 gauge17=CALLOUT_SmallJets!CALLOUTMIN, 0,0,0,0 gauge18=CALLOUT_SmallJets!CALLOUTAPPMIN, 0,0,0,0 Save what you have added on the Panel.cfg. Hope this helps.
  2. jahurz

    Fokker 50 GSX

    Dug up this plane after a while and did some modification to enable GSX Lvl 2 Passengers add the following into AppData\Roaming\Virtuali\Airplanes\Carenado F50\gsx.cfg [exit1] pos = -0.25 6.00 -2.10 0.00 code = 1 name = passenger embeddedStair = -0.50 6.00 -2.10 -2.79 6.00 -3.39
  3. Just bought this scenery on a seperate pc with a seperate order no. And i'm looking at flat only SODE jetways and no buildings or runway and it seems the terminal has lots of lakes and swamps around and its only occurring on this pc. Support mention it must be some vector/mesh addon but i only have orbx global base pack and global vector installed. Could ORBX ftx Global be causing and issue but the other computer had the same set of add-ons without any issues.
  4. Again due to lack of documentation anywhere i'll just post the vspeeds and etc down below here. Data here is from an airline that no longer operates Fokker 50. Some data is NIL as the company does not use it but i believe other operators have data for it. Note data below is for dry runway conditions. Gross Weight: 14t Flaps 5: v1= 92kts vr= 92kts v2= 95kts vfr= 97kts vfto= 101kts Flaps 5 Take off length= 800m Flaps 10 NIL Flaps 15 NIL flaps 25 vref= 88kts flaps 35 vref= NIL Gross Weight: 15t Flaps 5: v1= 92kts vr= 92kts v2= 95kts vfr= 101kts vfto= 105kts Flaps 5 Take off length= 841m Flaps 10 NIL Flaps 15 NIL flaps 25 vref= 91kts flaps 35 vref= NIL Gross Weight: 16t Flaps 5: v1= 95kts vr= 95kts v2= 97kts vfr= 104kts vfto= 108kts Flaps 5 Take off length= 904m Flaps 10 NIL Flaps 15 NIL flaps 25 vref= 94kts flaps 35 vref= NIL Gross Weight: 17t Flaps 5: v1= 98kts vr= 98kts v2= 100kts vfr= 107kts vfto= 112kts Flaps 5 Take off length= 1014m Flaps 10 v1= 95kts vr= 95kts v2= 97kts vfr= 107kts vfto= 112kts Flaps 10 Take off length= 1005m Flaps 15 NIL flaps 25 vref= 94kts flaps 35 vref= 92kts Gross Weight: 18t Flaps 5: v1= 101kts vr= 101kts v2= 103kts vfr= 110kts vfto= 115kts Flaps 5 Take off length= 1139m Flaps 10 v1= 98kts vr= 98kts v2= 100kts vfr= 110kts vfto= 115kts Flaps 10 Take off length= 1125m Flaps 15 v1= 95kts vr= 95kts v2= 97kts vfr= 110kts vfto= 115kts Flaps 15 Take off length= 1045m flaps 25 vref= 99kts flaps 35 vref= 95kts Gross Weight: 18.5t Flaps 5: v1= 103kts vr= 103kts v2= 104kts vfr= 112kts vfto= 117kts Flaps 5 Take off length= 1210m Flaps 10 v1= 100kts vr= 100kts v2= 101kts vfr= 112kts vfto= 117kts Flaps 10 Take off length= 1190m Flaps 15 v1= 97kts vr= 97kts v2= 98kts vfr= 112kts vfto= 117kts Flaps 15 Take off length= 1130m flaps 25 vref= 101kts flaps 35 vref= 96kts Gross Weight: 19t Flaps 5: v1= 104kts vr= 104kts v2= 105kts vfr= 113kts vfto= 118kts Flaps 5 Take off length= 1285m Flaps 10 v1= 101kts vr= 100kts v2= 103kts vfr= 113kts vfto= 118kts Flaps 10 Take off length= 1265m Flaps 15 v1= 98kts vr= 98kts v2= 100kts vfr= 113kts vfto= 118kts Flaps 15 Take off length= 1163m flaps 25 vref= 102kts flaps 35 vref= 97kts Gross Weight: 19.5t Flaps 5: v1= 106kts vr= 106kts v2= 107kts vfr= 115kts vfto= 120kts Flaps 5 Take off length= 1370m Flaps 10 v1= 103kts vr= 103kts v2= 104kts vfr= 115kts vfto= 120kts Flaps 10 Take off length= 1345m Flaps 15 v1= 100kts vr= 100kts v2= 101kts vfr= 115kts vfto= 120kts Flaps 15 Take off length= 1235m flaps 25 vref= 103kts flaps 35 vref= 99kts Gross Weight: 20t Flaps 5: NIL[I believe there's permissible vspeeds unfortunately the paper i have the company does not permit flaps 5 take off with this gross weight] Flaps 10 v1= 104kts vr= 104kts v2= 105kts vfr= 116kts vfto= 121kts Flaps 10 Take off length= 1429m Flaps 15 v1= 101kts vr= 101kts v2= 102kts vfr= 116kts vfto= 121kts Flaps 15 Take off length= 1312m flaps 25 vref= 105kts flaps 35 vref= 100kts Gross Weight: 20.5t Flaps 5: NIL[I believe there's permissible vspeeds unfortunately the paper i have the company does not permit flaps 5 take off with this gross weight] Flaps 10 v1= 106kts vr= 106kts v2= 107kts vfr= 118kts vfto= 123kts Flaps 10 Take off length= 1517m Flaps 15 v1= 103kts vr= 103kts v2= 104kts vfr= 117kts vfto= 123kts Flaps 15 Take off length= 1394m flaps 25 vref= NIL exceed MLW flaps 35 vref= NIL exceed MLW Gross Weight: 20.8t Flaps 5: NIL[I believe there's permissible vspeeds unfortunately the paper i have the company does not permit flaps 5 take off with this gross weight] Flaps 10 v1= 107kts vr= 107kts v2= 107kts vfr= 118kts vfto= 124kts Flaps 10 Take off length= 1552m Flaps 15 v1= 103kts vr= 103kts v2= 104kts vfr= 118kts vfto= 123kts Flaps 15 Take off length= 1445m flaps 25 vref= NIL exceed MLW flaps 35 vref= NIL exceed MLW Additional notes -Fairly common to add 10knots to your vref landing. So for e.g if your vref is 99knots you'll be approaching at 109knots and maintaining down to about 100feet above the runway then you'll slow down to your vrefs. Do note you may even have to add more speed to your vref depending on wind conditions. -Flaps 35 approach is rarely used except for runway with lengths shorter than 1500m or approach that requires a very steep glideslope gradient. -Preferred take off flaps is 10 on the documentation i am reading. But i am sure for other airlines will prefer flaps 5 if the runway is long. Flaps 15 again for short runway depending on runway length and conditions. -Take off to acceleration height retract your flaps once speed is at vfr and check if the speed is at vfto switch engine management to clb and wait for the speed to climb to 140knots ias. Use climb mode ias 140. If you've outclimbed terrain or atc gives a go ahead use v/s +500fpm and wait for the speed to go up to 170knots ias and then engage ias climb at 170knots. Best climb would be your vfto+5kts but again only used when needed. -Taking off with tailwind is risky on short runway. Take note a direct tailwind of just 5knots might need you take 200m more runway than required on calm conditions. Hope this helps others.
  5. You cant simulate GPU on carenado unfortunately. Also you can use hotel mode anyways as i believe carenado does not include the actual limitation of it. In real life the Hotel mode cannot be operated with side to tailwind wind exceeding 5knots at any place you're parking at. It also cannot be used during front cargo loading as the heat coming from the engines is bad for the ground crew. On ground purely on battery, the voltage endurance gives u roughly about 25minutes to do your preflight up to starting up the engines. You can imagine how hot it can be over the tropics at certain airports where there is no GPU provided. There are times when you park and there's tailwind registered, the plane will be basically cold and dark on most of the turnaround phase and there's no air conditioning as hotel mode cannot be used. And passengers don't feel good in the cabin when the temperature is 30c above 😁.
  6. I thought this might be helpful for those wanting to set vspeeds for normal condition. Got this data from ATR performance chart book from a certain airline. Gross weight= 17t V1=104KTS V2=110KTS VAPP= 96KTS WHITE BUG= 121KTS RED BUG = 145KTS Gross Weight=18t V1=104kts V2=110KTS VAPP=99KTS WHITE BUG=125KTS RED BUG=149kts Gross Weight=19t V1=104kts V2=110KTS VAPP=102KTS WHITE BUG=129KTS RED BUG=153kts Gross Weight=20t V1=105kts V2=110KTS VAPP=105KTS WHITE BUG=132KTS RED BUG=157kts Gross Weight=21t V1=106kts V2=111KTS VAPP=108KTS WHITE BUG=136KTS RED BUG=161kts Gross Weight=21.5t V1=109kts V2=113KTS VAPP=109KTS WHITE BUG=138KTS RED BUG=163kts Gross Weight=22t V1=111kts V2=114KTS VAPP=111KTS WHITE BUG=139KTS RED BUG=165kts Gross Weight=22.5t V1=112kts V2=115KTS VAPP=113KTS WHITE BUG=140KTS RED BUG=167kts Gross Weight=23t [Take note 23t take off is only available on selected airlines that ordered such planes and i believe Carenado's version does not support it] V1=114kts V2=117KTS VAPP=115KTS WHITE BUG=141KTS RED BUG=169kts Additonal info: 1)Greenbug is your v1 and most v1s are the same with vr. 2)Redbug is your icing condition speeds meaning you never dip below the red bug speed with 0 flaps. 3)On approach it is fairly common to add vref+10kts on your vapp until down to below 100feet. So if your vapp is for e.g 112kts your approach would be around 122knots down to about 100feet above the airfield you would then slow down to your vapp. You have to take account of wind conditions as well but i guess this rough estimate would do its job. 4)ATR72-500 burns around 700kg fuel per hour so this should give u a rough estimate on fuel planning. 5)Initial climb would be your white bug speed+5kts. It is only recommended to climb with whitebug+5kts if you're trying to clear over terrain in good weather. Standard climb at acceleration height would be 170kts. 6)On one of our shortest runway with 1370m length we take off without packs on and no tailwind component is allowed. 7)Never operate hotel mode if you have tailwind component exceeding 5knots at the position your parking at. Reduced flaps landing configuration for flap 15 landing 17t vapp=107kts 18t vapp=111kts 19t vapp=114kts 20t vapp=117kts 21t vapp=120kts 22t vapp=124kts 22.5t vapp=125kts Well hope this helps.
  7. I have stutter fps with this plane. The only way to fix it was the press shift+6 and boot the plane in cold and dark.
  8. Hello again can u send a latest screenshot here? mine seems okay. Check your gpu drivers. I recall i have pitch black issue flying at night with some of the nvidia drivers i installed.
  9. For those interested in repainting here are some of the ATR72's with varying paint schemes in malaysia MASWINGS 9M-MWF BIMP EAGA livery 9M-MWB Old livery 9M-MWC Malaysia flag on old livery 9M-MWE New livery 9M-MWF Malaysia flag on new livery 9M-MWJ Strive to Excel sticker livery FIREFLY 9M-FYA standard livery 9M-FYB Negaraku livery 9M-FYD Selangor state livery 9M-FYG Panasonic Livery 9M-FYH Kedah football team livery 9M-FYJ Jom Jalan livery 9M-FYL Fantasia Aquapark livery Berjaya air 9M-TAG We have another carrier Malindo but their livery is mostly the same throughout the entire fleet.
  10. Hello. Carenado issued 2 version of cockpit panel scheme titled Texture.common and Texture.common2. Common 1 is the old brown wood scheme pre 2008 ATR72 were mostly delivered with this scheme. Common 2 is the blue scheme which is the ATR's current to go to up to even the ATR72-600. To decide which color panel scheme to use head to SimObjects\Airplanes\Carenado AT72. Locate any livery u want to amend, inside that livery folder you should see a texture.cfg file open it as notepad and amend as per below: Brown scheme add the following line: [fltsim] fallback.1=..\texture.Common For the blue scheme add the following line: [fltsim] fallback.1=..\texture.Common2 fallback.2=..\texture.Common Hope this helps.
  11. Head to carenado's website to install version 1.2 it has an even better accurate blue scheme. Do uninstall your previous installation first before updating.
  12. Hello everyone. I've managed to port in a blue cockpit scheme with files from another user who owns an ATR42. It seems to work at the moment. For those interested here are the files with readme instructions. Blue Cockpit textures Cheers!
  13. I've managed solved it! I initially check on my command prompt for any packets it seems i am not sending any information to Carenado activation servers when i press to verify my serial. I checked on my host file on windows 32 and found nothing particular. Decided to login to my D-LINK router under port blacklist to my surprise there were 50+ ports and urls being blacklisted including Carenado. Removing all this blacklist immediately solves the issue on serial verification. I think carenado could probably improve how the errors were displayed the "serial is not valid" error gives me the impression that there was something wrong with their servers or my serial number when it was actually my router blacklisting them. Hope this helps others. Best Regards.
  14. The cockpit panel colors were based on Carenado's demo video on youtube. Have not got this to install as of now unfortunately. I've tried installing with firewall and Antiviruses turned off and the serial still came out invalid. I manually type them as well and it came out the same. Am still waiting for ticket reply on Carenado's support. Regards.
  15. Just poured my money for the ATR72-500 and now being hit with serial invalid issues. I looked at other posts but there seems to be no answers. I've switched off firewall, AV etc, copy paste the serial from notepad to no avail. I've raised a ticket to carenado but am not sure how fast can they rectify the issue. Can anyone here help? Regards
×
×
  • Create New...