Osprey Question

T

thedude247

Guest
When I take my copy of Alphasim' V-22 and add a freeware add-on (rcbhca20.zip) from Flightsim, to get the true hover capability out of her, after it's added the gauges no longer display. The aircraft works, but not the gauges. :(

Any thoughts.:kilroy:
 
I dont have the V-22 but I do have the BA609 with the VTOL gauge for that model. Works brilliantly. If you're having a problem it's almost certainly because you didn't follow the install instructions properly, even if you think you did. Uninstall the gauge completely and start again, reading the manual, step by step. I'll bet it works second time around.

LPXO
 
That's just the thing, i did it 3 times over and it still doesn't work properly, I'm not sure what else could be the problem.:kilroy:
 
When I take my copy of Alphasim' V-22 and add a freeware add-on (rcbhca20.zip) from Flightsim, to get the true hover capability out of her, after it's added the gauges no longer display. The aircraft works, but not the gauges. :(

Any thoughts.:kilroy:

What do you mean by ..."the gauges no longer display." ??

Isn't the VTOL working, or do you have a problem with existing gauges after adding my addon ??
If it's this first: you DO have FSUIPC installed and working, right ??

Rob
 
What do you mean by ..."the gauges no longer display." ??

Isn't the VTOL working, or do you have a problem with existing gauges after adding my addon ??
If it's this first: you DO have FSUIPC installed and working, right ??

Rob

This is your add-on then I take it, right on. I'll go through this again, after installing the aircraft (which works fine as is, just won't hover) all the nessesary gauges and effects display correctly, no worries. No offence, but after I install the hover convertion, the gauges no longer display. I'm afraid to say, SHE'S WONKY.

And my computer will only accept the default version of FSUIPC fo some friggin reason, that I discovered a long time ago.

What do you think???:kilroy:
 
This is your add-on then I take it, right on. I'll go through this again, after installing the aircraft (which works fine as is, just won't hover) all the nessesary gauges and effects display correctly, no worries. No offence, but after I install the hover convertion, the gauges no longer display. I'm afraid to say, SHE'S WONKY.

And my computer will only accept the default version of FSUIPC fo some friggin reason, that I discovered a long time ago.

What do you think???:kilroy:
What do you mean by "default version" of FSUIPC ???

If you want to solve this, it's better to Email me directly (see my README for EMail address) and describe exactly what you installed and where.
Also, attach the panel.cfg file you are now using that gives this problem.
Because I'm sure you are doing something wrong; just don't know what yet :icon_lol:


:ernae: Rob
 
What do you mean by "default version" of FSUIPC ???

Well, there is FSUIPC in the Modules folder, and I didn't put it there, so I can only assume to say that it came with the Sim???:kilroy:

Am I Wrong.:monkies:
 
. . . .Am I Wrong.
Yep, 'fraid so dude. It was probably installed as part of something else you installed. . .not sure what though, but FSUIPC isn't installed with FS9 by default. One other thing. . .in FS9 at the top of the screen where the various option dropdowns are, do you see one that says "modules"?
 
One other thing, I've always encountered problems in the past when it came to updating FSUIPC. Like FS9 not fully opening all together, my computer isn't this big extravagant $3000 computer that most of you likely have, I don't. Thats why I don't put everything I want on my Sim, or my computer for that matter. I own a very basic computer system with basic graphics on an integrated chip-set.

I have to nickle and dime everything, including my sim. money doesn't grow on trees where I come from.

Anyway, I get off topic. So thats why I can get the proper FSUIPC to funtion on my Sim.:icon_lol:
 
I don't have any of those trees either and I run on a computer I paid $300 for that has both FS9 and FSX running perfectly, sorry OT there as well.

Go to this page,
http://www.schiratti.com/dowson.html
scroll down to the section for "FS2004" and download the version of FSUIPC you see there. Go into your modules folder in FS9 and remove the FSUIPC.dll file you have and replace it with the one you just downloaded. (after you unzip the download, there will be several other files as well, ignore those and just drop the new FSUIPC file into your modules folder).

FSUIPC shouldn't affect your computer in the manner you describe, so it's possible you have a very old version or corrupted version somehow. Also, as I asked in the previous post, make sure that inside FS9 you have a dropdown for "modules" and that it contains FSUIPC.
 
Alright, I'll go that. I'll get back to you after I see if it works or not.:icon_lol:
 
I'm afraid the situation is unchanged, the gauges in the panel as well as the VC still do not pisplay, the VC gauges get displayed as a picture though. I can't seem to upload a few pictures to show you, but i hope you get what I'm saying.

Here is the Panel.cfg, see what you can make of it.

// Panel Configuration file
// V-22 Osprey
// For ALPHA SIMULATIONS
// By Phil Perrott 10 July 2006
// Version 1.2
// Adapted by Rob Barendregt on 2 oct. 2007 with VTOL package rcbhca20.zip
// See comment for added gauges.
[Window Titles]
Window00=Main Panel
Window01=GPS

[VIEWS]
VIEW_FORWARD_WINDOWS=MAIN_PANEL,GPS_PANEL
VIEW_FORWARD_ZOOM=0.5
VIEW_FORWARD_DIR=5.0, 0.0, 0.0
VIEW_FORWARD_RIGHT_ZOOM=0.5
VIEW_RIGHT_ZOOM=0.5
VIEW_REAR_RIGHT_ZOOM=0.5
VIEW_REAR_WINDOWS=30
VIEW_REAR_ZOOM=0.4
VIEW_REAR_EYE=1.0, -0.2, -5.2
VIEW_REAR_DIR=160.0, 180.0, 15.0
VIEW_REAR_LEFT_ZOOM=0.5
VIEW_LEFT_ZOOM=0.5
VIEW_FORWARD_LEFT_ZOOM=0.5
VIEW_UP_ZOOM=0.5

//--------------------------------------------------------
[Window00]
file=OspreyPnl.bmp
size_mm=1024,768
position=7
visible=1
ident=MAIN_PANEL
sizeable=1
render_3d_window=1
window_size= 1.000, 1.000
window_pos= 0.000, 0.000
gauge00=ALPHA_V-22!MFD8, 232,554,208,208
gauge01=ALPHA_V-22!MFD9_O, 465,554,208,208
gauge02=simicons!ATC Icon, 323,534,12,12
gauge03=simicons!GPS Icon, 338,534,12,12
gauge04=simicons!Kneeboard Icon, 352,534,12,12
gauge05=simicons!Map Icon, 367,534,12,12
gauge06=beech_baron!Beacon Lights, 249,525,16,26
gauge07=beech_baron!Nav Lights, 234,525,15,26
gauge08=beech_baron!Pitch Trim, 181,580,23,63
gauge09=beech_baron!Gear Lever, 184,702,35,63
gauge10=beech_baron!Panel Lights, 266,525,16,26
gauge11=beech_baron!Landing Lights, 282,525,16,26
//gauge12=lear_45.spoiler, 202,580,28,62 // Removed; "spoiler" is controlled by VTOL gauge
//gauge13=ALPHA_V-22!spdbrk, 196,545,22,22 // Removed; "spoiler" is controlled by VTOL gauge
//gauge14=ALPHA_V-22!Rotors_Ind, 179,649,45,44 // Replaced by VTOL display
gauge15=ALPHA_V-22!AP, 840,560,150,90
gauge16=rcb-gauges!VSTOLControlIPC_Display, 179,649,47,44 // Added
//--------------------------------------------------------
[Window01]
Background_color=16,16,16
size_mm=150,250
position=8
visible=0
ident=GPS_PANEL
gauge00=gps!gps, 0,0,150,250

//--------------------------------------------------------
[Vcockpit01]
file=vpanel_1.bmp
background_color=0,0,0
size_mm=1024,1024
visible=0
pixel_size=1024,1024
texture=$vpanel_1
gauge00=ALPHA_V-22!MFD8, 13,8
gauge01=ALPHA_V-22!MFD9_O, 246,8
gauge02=ALPHA_V-22!ATT, 474,9
gauge03=ALPHA_V-22!ASI, 730,7,170,170
gauge04=ALPHA_V-22!ALT, 605,9,125,127
gauge05=ALPHA_V-22!COMPASS, 476,133,65,65
//gauge06=ALPHA_V-22!Rotors_Ind, 917,308,80,80 // Replaced by VTOL display
gauge07=ALPHA_V-22!MFD7, 100,450,460,340
gauge08=beech_baron!Beacon Lights, 42,902,26,49
gauge09=beech_baron!Nav Lights, 16,902,26,49
gauge10=beech_baron!Panel Lights, 68,902,26,49
gauge11=beech_baron!Landing Lights, 94,902,26,49
gauge12=simicons!ATC Icon, 174,918,26,26
gauge13=simicons!GPS Icon, 201,918,26,26
gauge14=simicons!Kneeboard Icon, 228,918,26,26
gauge15=simicons!Map Icon, 255,918,26,26
gauge16=beech_baron!Pitch Trim, 919,178,44,119
gauge17=beech_baron!Gear Lever, 924,400,66,118
//gauge18=lear_45.spoiler, 962,179,42,118 // Removed; "spoiler" is controlled by VTOL gauge
//gauge19=ALPHA_V-22!spdbrk, 934,108,42,42 // Removed; "spoiler" is controlled by VTOL gauge
gauge20=ALPHA_V-22!AP, 91,273,160,100
gauge21=rcb-gauges!VSTOLControlIPC_Display, 917,308,80,80 // Added
gauge22=rcb-gauges!VSTOLControlIPC_Function, 0,0 // Added
gauge23=dsd_xml2ipc!xml2ipc, 0,0 // Added
gauge24=rcb-gauges!V22RotorWashEffectControl, 0,0 // Added
gauge25=rcb-gauges!GenCorrect, 0,0 // Added

[8 Bit Colors]
color00=8,8,8
color01=49,49,41
color02=33,33,33
color03=41,49,41
color04=41,41,33
color05=41,41,41
color06=49,49,49
color07=57,57,57
color08=66,66,66
color09=33,33,24
color10=82,90,74
color11=74,74,74
color12=74,74,66
color13=57,57,49
color14=33,33,41
color15=82,82,82
color16=41,41,49
color17=74,74,82
color18=74,66,57
color19=24,24,33
color20=115,115,107
color21=8,8,16
color22=90,90,90
color23=90,90,82
color24=90,82,74
color25=123,115,99
color26=115,107,90
color27=41,49,57
color28=66,66,74
color29=99,99,99
color30=189,189,189
color31=99,107,90
[Default View]
X=0
Y=0
SIZE_X=8191
SIZE_Y=6143

**Remember that this is the panel after the Hover conversion.
 
ok, a couple of things that would help I think:
The exact specs on your system (memory, CPU speed, graphics card and amount of memory onboard and so on).

Also, where are the gauges for the Osprey, are they in the main gauges folder or are they inside the panel folder for the Osprey.

I understand what you mean about the gauges displaying as a picture but no gauges. The bmp they used for the VC texture has gauges on it it, they're just not functional, simply an image of the control panel, then they lay the actual gauges over those in the sim.
 
OK, in the read-me for the add-on(rcbhca20) says to move all panel related objects into the main V-22 panel folder, correct me if i'm wrong thats just what I read.:kilroy: As far as my system is concerned, everything works fine as is.

Thanks for taking the time to help me with this.:applause:
 
OK, in the read-me for the add-on(rcbhca20) says to move all panel related objects into the main V-22 panel folder, correct me if i'm wrong thats just what I read.:kilroy:
That's correct for the RCB gauge and related files, but the actual default gauges for the Osprey should remain in the main gauges folder I believe. Is that where they are now?

. . . . .As far as my system is concerned, everything works fine as is.
I realize that, but what I was asking was the specifics. It would help greatly to know what type of computer you have and the specs for the info I asked about.

Thanks for taking the time to help me with this.
No Problem at all.
 
Ok, one more question:
Do any of the gauges show up? maybe 3 or 4 but not all? I have a reason for asking, but I need to know if absolutely none show up or if there are actually a few that do.
 
As far as my computer specs are concerned;
  • 1.60GHz Processor
  • 2Gb RAM (Upgraded Last December)
  • Intel integrated Media Accelerator 900 graphics card
  • 160Gb Hard Drive
Nothing Fancy

The question about the gauges you asked, basically all the forward instrument panel gauges don't show up, except for a few light switches, the trim gauge, the gear switch, and the individual panel buttons. You know, the ones for individual screens like GPS, Engine, ATC, etc.
 
As far as my computer specs are concerned;
  • 1.60GHz Processor
  • 2Gb RAM (Upgraded Last December)
  • Intel integrated Media Accelerator 900 graphics card
  • 160Gb Hard Drive
Nothing Fancy

The question about the gauges you asked, basically all the forward instrument panel gauges don't show up, except for a few light switches, the trim gauge, the gear switch, and the individual panel buttons. You know, the ones for individual screens like GPS, Engine, ATC, etc.
Is it the correct version of The Osprey? The RCB gauge readme refers to V1.2 of the payware Alphasim Osprey.
 
Back
Top