Jump to content

Alabeo Robinson R66


Tenpin

Recommended Posts

Posted

I am writing this quickly without delay....NO GO on the Alabeo R66. I purchased it at PCaviator for $17 sale so if it did not work, well someday might HAVE to get acceleration IF to many aircraft required it..It will go in the closet of external hard drive. Just to make sure I went to my NEW Milviz 407 and it works BEAUTIFULLY. I DO NOT have acceleration..(the problem).

      I have my fsx running still that is how I did NOT want to leave you hanging. The R66 will have engine running if on the Tomahawk I left it running then went to the R66. NO throttle, keyboard or otherwise. I have original Microsoft forcefeedback sidewinder, Ch throttles, Ch pedals, Ch yoke, Saitek TPM, Saitek Cessna Licensed Trim Wheel and ELITE AVIONICs radio stack.  On the Milviz the collective DOES NOT move but if I assign Ch throttle IS the collective and the PROP runs the NP RPM and will run it perfectly. SO>>> just not having the collective visually move is the ONLY issue. Also the CONFIGURATION does NOT work correctly at all, (sure this is because it is ONLY designed for Acceleration). BUT I experimented and a bit complicated but got my rxp430 and 530 in the panel. COULD NOT get the transponder in or back in????  I put it back to original avionics panel and made a rxp430 popup which is about all there would be realistically. PERFECT setup...NOTE: I LABELED IT " Radio Stack " this keeps it conflicting with the GPS that they have yet still recognizes the rxp, also the configuration DOES somewhat work and MY Window05 does NOT conflict.

 

// This Panel.cfg file created by FS Panel Studio panel editor utility - http://www.fspanelstudio.com

[Window Titles]

Window00=Configuration Manager
//Window01=GPS
//Window02=Reality XP GNS 430 WAAS - RXP_CONFIG_TOOL - DO NOT CHANGE
//Window03=Reality XP GNS 530 WAAS - RXP_CONFIG_TOOL - DO NOT CHANGE
//Window04=Reality XP DropStack
Window05=Radio Stack

 

[Window00]
Background_color=0,0,0
size_mm=920,440
window_size_ratio=1.000 
position=0
visible=0
ident=40
window_size= 0.001, 0.001
window_pos= 0.000, 0.000

 

gauge00=MV407CM!cm_av1,  16,295,121,30
gauge01=MV407CM!cm_av2,  136,295,121,30
gauge02=MV407CM!cm_av3,  29,328,121,30  
gauge03=MV407CM!cm_av4,  149,328,121,30
//gauge04=MV407CM!cold,  55,392,121,30   
//gauge05=MV407CM!cm_rtf,  175,392,121,30
gauge06=MV407CM!cm_vis_01,  15,168,16,16
gauge07=MV407CM!cm_vis_02,  15,201,16,16
gauge08=MV407CM!cm_vis_03,  15,234,16,16
gauge09=MV407CM!cm_tan,  44,360,121,30
gauge10=MV407CM!cm_save,  164,360,121,30

[Window05]
size_mm=456,191
window_size=0.5
position=8
BACKGROUND_COLOR=0,0,0
VISIBLE=0
ident=RADIO_STACK_PANEL
zorder=4

gauge00=rxpGNS!GNS430,            0,0,456,191

//-----------------------------------------------------------------------------
[Vcockpit01]
file=Bell_407.bmp
Background_color=0,0,0
size_mm=1024,1024
visible=1
pixel_size=1024,1024
texture=$Bell_407

gauge00=Milviz_Sound!FBGS_XMLSound,  0,0,1,1,SimObjects\\Rotorcraft\\MILVIZ_Bell407\\Bell407XML_Sounds#30
gauge01=Bell407!Com22,  8,258,1010,107
gauge02=Bell407!Xpdr,  6,409,1012,112
gauge03=Bell407!Com11,  8,104,464,102
gauge04=Bell407!Nav11,  552,104,464,102
gauge05=Bell407!TRQ_LCD,  8,542,236,71
gauge06=Bell407!MGT_LCD,  8,647,236,71
gauge07=Bell407!N1_LCD,  9,749,236,71
gauge08=Bell407!FUEL_LCD,  2,851,236,71
gauge09=Bell407!boot_timer,  2,1,1,1
gauge10=Bell407!Chronometer,   270,410,630,630
gauge11=MV_B407_STF!STF, 0,0,1,1,0

//--------------------------------------------------------
[Vcockpit02]
Background_color=0,0,0
size_mm=1024,1024
visible=1
pixel_size=1024,1024
texture=$cl_1

gauge00=MV_B407_LT!L1,  0,0,1024,1024, 1

//--------------------------------------------------------
[Vcockpit03]
Background_color=0,0,0
size_mm=1024,1024
visible=1
pixel_size=1024,1024
texture=$cl_2

gauge00=MV_B407_LT!L2,  0,0,1024,1024, 2

//--------------------------------------------------------
[Vcockpit04]
Background_color=0,0,0
size_mm=1024,1024
visible=1
pixel_size=1024,1024
texture=$cl_3

gauge00=MV_B407_LT!L3,  0,0,1024,1024, 3

//--------------------------------------------------------
[Vcockpit05]
Background_color=0,0,0
size_mm=1024,1024
visible=1
pixel_size=1024,1024
texture=$cl_4

gauge00=MV_B407_LT!L4,  0,0,1024,1024, 4

//--------------------------------------------------------
[Vcockpit06]
Background_color=0,0,0
size_mm=1024,1024
visible=1
pixel_size=1024,1024
texture=$cl_5

gauge00=MV_B407_LT!L5,  0,0,1024,1024, 5

//--------------------------------------------------------
[Vcockpit07]
Background_color=0,0,0
size_mm=1024,1024
visible=1
pixel_size=1024,1024
texture=$cl_6

gauge00=MV_B407_LT!L6,  0,0,1024,1024, 6

//--------------------------------------------------------
[Vcockpit08]
Background_color=0,0,0
size_mm=1024,1024
visible=1
pixel_size=1024,1024
texture=$cl_7

gauge00=MV_B407_LT!L7,  0,0,1024,1024, 7

//--------------------------------------------------------
[Vcockpit09]
Background_color=0,0,0
size_mm=1024,1024
visible=1
pixel_size=1024,1024
texture=$cl_8

gauge00=MV_B407_LT!L8,  0,0,1024,1024, 8

//--------------------------------------------------------
[Vcockpit10]
Background_color=0,0,0
size_mm=1024,1024
visible=1
pixel_size=1024,1024
texture=$cl_9

gauge00=MV_B407_LT!L9ON, 0,0,1024,1024, 10

//--------------------------------------------------------
[Vcockpit11]
Background_color=0,0,0
size_mm=128,128
visible=1
pixel_size=128,128
texture=$cl_10

gauge00=MV_B407_LT!L11,  0,0,128,128, 12

//--------------------------------------------------------
[Vcockpit12]
Background_color=0,0,0
size_mm=1024,1024
visible=1
pixel_size=1024,1024
texture=$cl_11

gauge00=MV_B407_LT!L10,  0,0,1024,1024, 11

//--------------------------------------------------------
[Vcockpit13]
Background_color=0,0,0
size_mm=1024,1024
visible=1
pixel_size=1024,1024
texture=$cl_12

gauge00=MV_B407_LT!L9OF, 0,0,1024,1024, 9

//--------------------------------------------------------
[Vcockpit14]
file=C310_VC_01.bmp
size_mm=1024,1024
visible=0
pixel_size=1024,1024
texture=$C310_VC_01

gauge00=MV-407-XML_P3Dv2!FBS_GNS430_2,  0,367,640,262
gauge01=MV-407-XML_P3Dv2!KR 87 ADF,  0,630,640,134

//--------------------------------------------------------
[Vcockpit15]
Background_color=0,0,0
size_mm=512,512
visible=1
pixel_size=1024,1024
texture=$C310_VC_02
gauge00=MV-407-XML_P3Dv2!FBS_GTX330,  0,376,512,136
//gauge00=MV-407-XML_P3Dv2!FBS_GTX330,  0,376,512,136
//gauge01=MV-407-XML_P3Dv2!FBS_GNS530_1,  0,0,512,374
gauge01=MV-407-XML_P3Dv2!FBS_GNS530_1,  0,0,512,374
//--------------------------------------------------------
//--------------------------------------------------------
[Vcockpit16]
Background_color=0,0,0 
size_mm=1024,1024
visible=0
pixel_size=1024,1024
texture=$C310_VC_03

//gauge00=rxpGNS!GNS430, 0,10,1024,433

//--------------------------------------------------------
[Vcockpit17]
Background_color=0,0,0 
size_mm=512,512
visible=0
pixel_size=1024,1024
texture=$C310_VC_04

//gauge00=MV-407-XML_P3Dv2!FBS_GTX330,  0,376,512,136
//gauge00=rxpGNS!GNS530,  0,8,512,384

//--------------------------------------------------------
[Vcockpit18]
file=C310_VC_01_FR.bmp
size_mm=1024,1024
visible=0
pixel_size=1024,1024
texture=$C310_VC_05

//gauge00=MV-407-XML_P3Dv2!FBS_GNS430_2d,  0,707,640,262
//gauge01=MV-407-XML_P3Dv2!BK_AudioPanel,  0,0,640,128
//gauge02=MV-407-XML_P3Dv2!FBS_GNS530_1d,  0,103,640,468
//gauge03=MV-407-XML_P3Dv2!FBS_GTX330,  0,571,640,136

//--------------------------------------------------------
[Vcockpit19]
file=C310_VC_02_FR.bmp
size_mm=512,512
visible=0
pixel_size=1024,1024
texture=$C310_VC_06
//gauge00=MV-407-XML_P3Dv2!FBS_KAP140,  0,106,512,131
//gauge01=MV-407-XML_P3Dv2!FBS_KR 87 ADF,  0,0,512,106

//--------------------------------------------------------


Day=255,255,255
Night=255,255,255
Luminous=255,0,0

[Default View]
X=0
Y=0
SIZE_X=8192
SIZE_Y=6143

 


I meant to say " this keeps it FROM conflicting with theres. SORRY keith

Posted

Spent 15 minutes on writing to ROCKLIFFE and my whole post disappeared??? maybe I pushed the wrong thing.

    Well anyway I just purchased the Alabeo R66 with NO LUCK.. not like the Milviz 407 which DOES work on my NON acceleration FSX.  I have only had it 30 minutes and wanted to let you know.  PERHAPS I might find a fix. I used my CH throttle for collective on the Milviz 407 and the Prop controls the N2 RPM work quite perfectly, BUT the collective DOES NOT visually move. Since I do not have TrackIR looking down to see it would not happen that much anyway. I DO have EZ dok. Windows 8 with CH throttle, Ch Yoke, Ch Pedals, Original Microsoft Forcefeedback Sidewinder, Saitek TPM, Saitek Cessna licensed Trim Wheel and ELITE AVIONICS panel.

    I CAN get the motor running by putting on the tomahawk WITH engine running and then switching to the R66 but there is NO control on throttles or collective??? I DO believe IF this guys works with only SP1 AND SP2 I MIGHT find a fix in time..it maybe that he is mistaken and does not realize he HAS acceleration, because it is a bit confusing. FSX GOLD, FSX deluxe, Gold being deluxe plus acceleration??? not saying he is ignorant but just a Maybe??

Posted

Dude, you should install the Acceleration pack, is extremely complicated and full of bugs all you said, and that's not the reality, I have it on acceleration and there's no even minimal problem with it...one of the most very well done helicopter out there, even quite better than Nemeth and Milviz with their version 5 (or so), of the Bell 407...honestly, this helicopter is very very well done...

 

So, install acceleration and see if all those bugs that appeared just to you, disapear...

Posted

I've just seen the sales blurb... it does in fact state Acceleration is needed, which I don't have and not inclined to purchase it just to get the bloody thing to work!! Hmm, unhappy... this is the only addon I've ever bought, where it's been stated that Acceleration is needed for it to operate correctly :mad:

Howard
MSI Mag B650 Tomahawk MB, Ryzen7-7800X3D CPU@5ghz, Arctic AIO II 360 cooler, Nvidia RTX3090 GPU, 32gb DDR5@6000Mhz, SSD/2Tb+SSD/500Gb+OS, Corsair 1000W PSU, LG Ultragear 48"4K, MFG Crosswinds, TQ6 Throttle, Fulcrum One Yoke
My FlightSim YouTube Channel: https://www.youtube.com/@skyhigh776

  • 1 year later...
Posted

As far as I'm concerned, it's money down the drain, as I can't get any resemblance of flight! I did send a support request directly to Alabeo but they haven't replied, that was weeks ago!   :angry: They certainly won't be having any more of my money.

 

Old thread and quote, I know.  Nevertheless, this is where I wound up when my new R66 was a decorative piece on the ramp with an engine running and static blades.  Who would have thought I finally found an aircraft that needed Acceleration Pack to run?

 

Anyway, in hopes of adding to the knowledge base if anyone else ever comes looking, I renamed the .air file to .sav, took the .air file from the Bell 206B, dropped it into the R66 folder, renamed it to r66.air and all is well!

  • 11 months later...

Archived

This topic is now archived and is closed to further replies.

  • Tom Allensworth,
    Founder of AVSIM Online


  • Flight Simulation's Premier Resource!

    AVSIM is a free service to the flight simulation community. AVSIM is staffed completely by volunteers and all funds donated to AVSIM go directly back to supporting the community. Your donation here helps to pay our bandwidth costs, emergency funding, and other general costs that crop up from time to time. Thank you for your support!

    Click here for more information and to see all donations year to date.
×
×
  • Create New...