_ben

I had the same problems with the Carenado Malibu 530 and 430 virtual cockpit. After many attempts the screen is in the right place, but on the left side the 'positions' of the different buttons, dials were moved relative to the visible carenado buttons 530 Start {A bit to LEFT of start button} V/C Switch Button {Way to left AND Tiny spot to find} etc

hard to argue

Needed to change -values on 2d panels // To zoom 430 up/down click [top of gauge , not interior screen] // can't zoom from vc , but rid down 2d window with this code // not sure why cant zoom up 530, IDENT 0 [initial carenado], 255 ms gps don't work, put in made up no // very tiny spots on vc to click vc, to left (usually) of vc buttons on left // 2d windows easier to us. [Window00] //ident=0 //ident=255 // no difference ident=10004 // make up no //gauge00=MPI_GNS!GNS530,0, 0,528,310, 1:2:-1 gauge00=MPI_GNS!GNS530,0, 0,528,310, 1:2:10004 [Window01] //gauge00=MPI_GNS!GNS430,0,0,493,310, 2:2:-1 gauge00=MPI_GNS!GNS430,0,0,493,310, 2:2:10010

I thought the original requester had left, just realise different posters. Good and Bad news vc and 2d windows look ok but left hand side of 430 an bottom 530 not responding - still experimenting. //------------------------------------------------- [Vcockpit02] //530 comment out carenado version //gauge01=GPS_530_3D_P46350P!gps_500, 7,337,493,358 gauge01=MPI_GNS!GNS530,4,333,506,360, 1:1:-1 //430 comment out carenado version //gauge03=GPS_430_3D_P46350P!GNS430_nc2, 517,259,497,258 gauge03=MPI_GNS!GNS430, 500,262, 514,238, 2:1:-1 //------------------------------------------------- //------------------------------------------------- [Window01] //530 comment out carenado version //gauge00=GPS_430_3D_P46350P!GNS430_nc2, 0,0,528,310 gauge00=MPI_GNS!GNS430,0,0,493,310, 2:2:-1 //------------------------------------------------ [Window00] // different size // size_mm=512,512 size_mm=528,310 //window_size= 0.300, 0.388 window_size = 0.298, 0.392 //430 comment out carenado version //gauge00=GPS_530_3D_P46350P!gps_500, 0,0,512,512 gauge00=MPI_GNS!GNS530,0, 0,528,310, 1:2:-1

Above the transponder (they look like warning lights , instead of switches ( just found it :-) )

There is a specific OPUS forum here at AVSIM - I can't seem to paste the address. AVSIM FORUMS/COMMERCIAL SUPPORT FORUMS/OPUS as well as the official page - I can't seem to post it either But needless to say Stephen has posted he's on holiday till next weekend ::-) If the server icon is on your desktop - open it as administrator OPUS FSX Server Click configuration button make sure your Simulator type and location is selected and correct location given The default is probably best not to alter until you know it more { check Live Wx Engine [box] is ticked} click ok If FSX is not running Start FSX Although flight plans are needed for most things if you just start FSX for T and G's Go to AIRPORT Once ready Open up OPUS Server CLick Weather Button Click Update Weather button BOTTOMM right before OK button Go back to FSX If there's weather to be seen hopefully you'll see it - calm , cloudless day of course won't show anything I think that will work ( I've usually put in flight plans but Stephen assured me it should work as above ) No flames if it doesn't , please.

[actually I only have DXT5 Texture Compression - I thought I had 32BIT] Top of REX4 Texture Direct Dialog (i) * - x -The astererisk Config Settings & Optimisation FS Folder TEXTURE RESOLUTION 512 Low-Level Clouds 512 (Low Res) High/Mid Level clouds Texture Compression DXT5 ( both low and high)

I have great improvement ( fps and looks) when I use 512 32bit clouds I think they look much better than the higher resolution versions -softer. Rex 4, DX10 Fixer

I have that happen if I use a Mindstar G430 aircraft - nothing happens until shutting down P3D

As above This company puts real life problems into their aircraft Nothing can't be broken and nothing can't be fixed If you idle on the ground without some mixture leaning, you will get spark plug fouling It's all easily(and cheaply:-) ) fixed with the method above It certainly pushes you to not ignore flap extension speeds ,etc

I'm no expert, but; It has many tweaking options other than just Antialiasing If you get the DX10Fixer, there are many suggestions on helpful changes - AA, Anisotropic Filtering, VSync, etc

I think Paul J says you need to match DX10Fixer with Inspector settings: ie 2X and 2X or 4X with 4X etc

they sure do there's a cabin ventilation knob on right lower panel ( not the heating knob )

SPOT view seems to smooth out Instant replay of jerky movements

Interesting post. Thanks My search was similar, REX4 (I like 512LO softerclouds at ground,no edges, 1024HI CU nice edges,),ASN,ORBX Austr.DX10Fixer, i7, 16GB580 NVidia,Insp.4xAA, vsync half, 30fps, NO OVC 28, OVC 12 and down! If I reduce FSX AI car traffic down from 15pc to 2pc OVC steady 20s ! Ben

I had time for a flight :-)

IF you have the extra PAYWARE Voices from Ivona, you can edit letters or words to be pronounce the way you like. The only trouble is with AI I have a favourite airport, Hamilton Island, Hamilton I. The initial pronunciation was Hamilton I (eye), I changed I. to say ISLAND, so my controllers (IVONA VOICES) say Hamilton Island :-) UNFORTUNATELY. the AI seemed to have a different vocabulary, Hamilton IS.(is) which is very annoying, and at the moment, I haven't worked out a solution Because the FOUR voices cost me Hundreds of dollars, I'm reluctant to spend that much again for the AI voices, which I currently use the Freeware voices (which I don't think can be edited)

Still no joy - thanks for suggestion.

My Installation problem is the Controller won't open. I think everything is installed in FSX,but, My FSX is on E:\... I think the Controller is trying to use C;\.. BUT I can't open it to change the directory!

IVONA: wind: The ability to change default WINE-d to WIN-d PA 28 to P A 28, etc is unbeatable. Volume, speed of each speech can be changed too, so with these for Controllers, and the free voices for AI pilots, it's not perfect; but it's pretty close.:-)

Yes Use the joystick setup program in the Vox Program menus. FSX: It won't work until you're in FSX and you run the program from the menu. VoxATC dialog: If you [Enable] it the key will work, if you [Disable] it won't. ben

Wow also.

Understood :mellow: My aim was to inform those interested in the current status of an (underappreciated?), complete, easy and still being developed ATC program.

I am no expert, recent user; however in response to the above, the VoxATC manual states This version of VoxATC has five types of emergency currently defined, these are: engine failure fuel low hydraulic failure avionics failure passenger critically ill You can make any standard request, but will most frequently want vectors to the nearest suitable airport. Again from the manual: The code used to designate a procedure (SID/STAR), is usually an abbreviated form of the procedure name. VoxATC must translate this to the designation that will be used in ATC comms. This process is not perfect and in some cases, can produce incorrect spoken designations. The Procedure Pronunciation Editor allows for the definition of replacements for unpronounceable parts of a procedure name on an airport by airport basis. Load Airport To start, select Load Airport on the menu and enter the ICAO code of the airport into the displayed dialog. A tree view on the left side of the form displays the airport name and two sub items SIDS and STARS Again from the manual Flying in UK / European Airspace VoxATC uses different phraseology and procedures when you are flying in the UK or Europe. Frequencies are given using 'decimal' instead of 'point'. QNH and QFE are used for altimeter setting. The transition altitude is 3500. 'Pass your message' replaces 'go ahead' 'Ready for departure' replaces 'ready for takeoff'. A UK supplement is available that adds LARS, DACS, MATZ and FISO and A/G phraseology, see VoxATC.com for further information SO I hope you can see it is a fairly comprehensive effort Again, just from a user , no company affiliation