Issues with aligning virtual cockpit gauge panel textures, help?

[A306capt9]

Hey, everyone!! I am still working on my aircraft . However, 3ds max makes my bmp's flippy & flipping around my textures for my overhead panel (upper part) & it's hard for me to align. How do I get the BMP/move the bmp around to align to this part of the panel & for the "$" textures to appear in FSX (since I tried having them appear even at 512x512 & the gauges don't appear & the whole VC is black)?

to make it look like this?:

 

[tgibson]

I use a UVW Unwrap modifier, press the Edit button, and drag the panel vertices around until aligned with the proper area of the bitmap. Be careful not to destroy the proportions.

 

[tgibson]

Oh, perhaps you want to align your mapping to the angled surface? This can be done in two ways:

1. After adding a UVW Map modifier, click on the little plus sign below the modifier name in the stack and click on Gizmo. You can rotate the mapping plane to match the angle of your panel.

2. You can use the View Align button, after aligning your view to the relevant polygon. Here is how you do that, copied from a previous forum post:

Tip: Gmax Aligning view with a surface

Hi all,
i have been looking high and low for a way to look perpendicular at a surface of an object which is under an angle in space.
So the usual top, left, bottom etc views are not usable here and hand-aligning the view does not always get me the result i need.

I make extensive use of the 2.5D snap and for that to work properly you must have a fixed view such as left, top, etc.
But it also works when in a grid view, so read on...

Since gmax and max do not have a ready made function for this (to my knowledge) i googled a bit and found this:

-Create a grid on the required surface.
You can do that under the Create tab - Helpers (the button with the tape-measure icon) - Grid.

Make sure autogrid is ticked, this makes sure that the new grid is created ON the surface that you need. When creating the grid move your cursor over the surface and you see the orientation of the gizmo align with the surface as you move from empty space to the surface.
Just click and drag to create the grid.

-After the grid has been created, you must activate it by rightclicking on it and from the quad menu choose "activate grid".

-Now that the grid is active, right click on the text in the upperleft corner of your view (where it says left, right, user, etc). From there choose views - grid views - (and in this case) top.
This will have you looking down on the grid that you just created. Your view is now perfectly aligned with the top surface of the object.

Hope this comes in handy for some of you!!

Btw the autogrid checkbox is also available with the creation of primitives such as cylinders, boxes, lines etc. You can use this to easily "build" things on top of each other on the fly, for instance a box on top of a cylinder. No need for elaborate aligning of stuff afterwards, or creation loads of user grids. This just creates a temporary grid that you can create your primitive on. Works very well also!

grt
Willem

 

[A306capt9]

I use a UVW Unwrap modifier, press the Edit button, and drag the panel vertices around until aligned with the proper area of the bitmap. Be careful not to destroy the proportions.

I managed to map the vc. I did upper overhead and lower overhead by splitting them into 2 separate textures (& created 1 more for the autopilot, screen and display controls). Now the problem is , the vc textures are black. How do I get the textures to not appear black in FSX? I even put the textures to power of 2 so that it doesn’t happen, I even added them into the model as a non “$” texture to see if they would appear , & without gauges (as a test to see if the texture appears )

 

[tgibson]

In FS2004 and FSX the daytime VC gauge area textures must be placed into the panel folder, not the plane's texture folders. Night textures (_L type) go into the plane's texture folders though.

Perhaps an example might help?

Here is one of my VC sections in the panel.cfg file:

[Vcockpit01]
file=pan1.bmp
Background_color=0,0,0
size_mm=512,512
visible=0
window_size= 0.320, 0.427
pixel_size=1024,1024
texture=$pan1
window_pos= 0.000, 0.000

The gauge panel texture is called $pan1. But I wanted a texture to cover this area as well, which is called pan1.bmp. This is placed into the panel folder, along with the 2D panel bitmaps. I also have set up a night texture, panl_L.bmp, which is placed into each plane's texture folders.

Note that the more Vcockpit sections you have, the harder on frame rate and the jerkier the needle movements, at least in FS2004 and FSX. I limit myself to two.

 

[A306capt9]

In FS2004 and FSX the daytime VC gauge area textures must be placed into the panel folder, not the plane's texture folders. Night textures (_L type) go into the plane's texture folders though.

Perhaps an example might help?

Here is one of my VC sections in the panel.cfg file:

[Vcockpit01]
file=pan1.bmp
Background_color=0,0,0
size_mm=512,512
visible=0
window_size= 0.320, 0.427
pixel_size=1024,1024
texture=$pan1
window_pos= 0.000, 0.000

The gauge panel texture is called $pan1. But I wanted a texture to cover this area as well, which is called pan1.bmp. This is placed into the panel folder, along with the 2D panel bitmaps. I also have set up a night texture, panl_L.bmp, which is placed into each plane's texture folders.

Note that the more Vcockpit sections you have, the harder on frame rate and the jerkier the needle movements, at least in FS2004 and FSX. I limit myself to two.

Ah, I see. Vcockpit still reads as black. MCX reads the vc $textures. I tried the panel config vc section in your panel.cfg file but textures are black. What could this be? & I have attached my plane for you to take a look at it:
https://filebin.net/pkjo7pb98dnpaqjj

 

[tgibson]

Hi,

OK, after a couple of hours of trying, I finally figured this out. It's something I wasn't aware of before, so I learned something from the exercise, thanks.

You have your VC gauge textures assigned as:

$G550loweroverhead
$G550upperoverhead
$G550dashanscreens

I cannot make these names work. But if I change them to:

$lower
$upper
$dash

And change the lines in the panel.cfg file to match - example:

texture=$upper

then the textures display fine. I didn't need to change the names of the background textures - example:

file=G550upperoverhead.bmp

these names worked OK.

So apparently you need simple names (perhaps less than 8 characters long) for the virtual gauge textures.

One final thing - in the Material Editor you need to change the name of the Emissive texture for your virtual gauge textures. For example:

Diffuse: $upper
Emissive: upper_L.bmp

Yes, no BMP for the diffuse, but include BMP for the Emissive. The Emissive texture name can be anything you want, but needs to be spelled out here.

You can probably do the same thing instead in your 3D CAD program you are using to build the plane, I assume, but if you are using MCX for final export check it there too.

Hope this helps,

 

[tgibson]

Oh, one more thing. In your lower overhead texture you stretched it so the rectangle shape filled the entire square. This is not necessary, just paint the actual rectangle into the square texture, leaving the extra blank. Then map the surface only onto the painted rectangular portion. The unused portion of that texture can then be used for another area in the VC without having to create a new VCockpit section in the panel.cfg file. Thus you can populate multiple areas in the VC using a single virtual texture.

 

[tgibson]

Finally the current Eyepoint line in the Views section of the aircraft.cfg file puts me over the top of the fuselage when in the VC.

If this is true for you this line gets me close:

eyepoint = 37.98, -1.15, 1.15

 

[A306capt9]

Finally the current Eyepoint line in the Views section of the aircraft.cfg file puts me over the top of the fuselage when in the VC.

If this is true for you this line gets me close:

eyepoint = 37.98, -1.15, 1.15

Ah, i see. I tried displaying the $ textures again. Now they are grey. Also, I am a visual learner. Can you show me with pictures on how to display these gauges? I feel stuck after trying so many things on it, even if i referenced the .bmp file:

 

[A306capt9]

Oh, one more thing. In your lower overhead texture you stretched it so the rectangle shape filled the entire square. This is not necessary, just paint the actual rectangle into the square texture, leaving the extra blank. Then map the surface only onto the painted rectangular portion. The unused portion of that texture can then be used for another area in the VC without having to create a new VCockpit section in the panel.cfg file. Thus you can populate multiple areas in the VC using a single virtual texture.

Ok, now I was able to display the VC textures & able to see them in FSX. now i will add gauges to the panel

 

[tgibson]

Glad to help.

 

[A306capt9]

Glad to help.

thanks!! also, how do you make the HUD transparent?

 

[A306capt9]

Glad to help.

I linked all the gauges. the pfds shows up black & when i switch to the 2d panel, it crashes. what could this be? :


Faulting application name: fsx.exe, version: 10.0.61637.0, time stamp: 0x46fadb14
Faulting module name: ui.dll, version: 10.0.61637.0, time stamp: 0x46fadb59
Exception code: 0xc0000005
Fault offset: 0x0002b350
Faulting process id: 0x1220
Faulting application start time: 0x01d68a550970360e
Faulting application path: C:\Microsoft Flight Simulator X\fsx.exe
Faulting module path: C:\Microsoft Flight Simulator X\ui.dll
Report Id: bd63a571-f648-11ea-8f18-cb4334d43cd9

& here is my panel.cfg for it that you can test/ troubleshoot:

// This Panel.cfg file created by FS Panel Studio panel editor utility - http://www.fspanelstudio.com
// Built Monday, September 14, 2020 at 01:02 FSPS Build:20207

[Window Titles]
Window00=Main Panel
Window01=HUD
Window02=HUD Background
Window03=Ground Handling
Window04=Overhead
Window05=Standby
Window06=PEDESTAL
Window07=GPS
Window08=Rudder Trim
Window09=MCDU


[VIEWS]
VIEW_FORWARD_DIR=-1.000, 0.000, 0.000



//--------------------------------------------------------
[Window00]
Background_color=0,0,0
size_mm=1920,1080
position=0
visible=1
ident=MAIN_PANEL
window_size= 1.000, 1.000
window_pos= 0.000, 0.000
zorder=1

gauge00=G550!G550 00 Background,  0,0,1920,1080
gauge01=Config!Config,  0,0,20,20
gauge02=G550!G550 00 XUpdate1,  0,0,20,20
gauge03=G550!G550 00 XUpdate2,  0,0,20,20
gauge04=G550!G550 00 Display Control Panel,  455,344,683,154
gauge05=G550!G550 00 Autopilot,  1138,344,782,154
gauge06=G550!G550 00 DU1 Synoptic,  134,520,693,526
gauge07=G550!G550 00 DU2 Synoptic,  863,520,693,527
gauge08=G550!G550 00 DU2 Mouse Update,  0,0,20,20
gauge09=G550!G550 00 IRS Switches,  1578,501,95,578
gauge10=G550!G550 00 DU3 Synoptic,  1688,520,231,526
gauge11=G550!G550 00 DU Update1,  0,0,20,20
gauge12=G550!G550 00 DU Update2,  0,0,20,20
gauge13=G550!G550 00 Icons,  20,428,249,25
gauge14=G550!G550 00 Master Warning Lights,  280,  365 ,161,123
gauge15=G550!G550 00 Clock,  22,691,97,97
gauge16=G550Sound!Sound,  2,2,2,2,\G550Sounds\Sound.ini


//--------------------------------------------------------
[Window01]
Background_color=0,0,0
size_mm=1920,1080
position=0
visible=0
ident=10050
window_size= 1.000, 1.000
window_pos= 0.000, 0.000
zorder=2

gauge00=G550!G550 00 HUD Background,  482,70,965,784


//--------------------------------------------------------
[Window02]
Background_color=0,0,0
size_mm=1920,1080
position=0
visible=0
ident=10051
window_size= 1.000, 1.000
window_pos= 0.000, 0.000
zorder=3

gauge00=G550!G550 00 HUD Panel Background,  0,0,1920,1080
gauge01=G550!G550 00 HUD PFD,  482,85,965,784
gauge02=G550!G550 00 Display Control Panel,  455,922,683,154
gauge03=G550!G550 00 Autopilot,  1138,922,782,154
gauge04=G550!G550 00 Master Warning Lights,  280,939,161,123
gauge05=G550!G550 00 Icons,  20,1005,249,25
gauge06=G550Sound!Sound,  2,2,2,2,\G550Sounds\Sound.ini


//--------------------------------------------------------
[Window03]
Background_color=0,0,0
size_mm=330,645
position=2
visible=1
ident=10033
window_size= 0.172, 0.597
window_pos= 0.000, 0.000
zorder=4

gauge00=G550!G550 00 Ground Handling Panel,  0,0,330,645


//--------------------------------------------------------
[Window04]
Background_color=0,0,0
size_mm=980,1042
position=2
visible=0
ident=OVERHEAD_PANEL
window_size= 0.379, 0.714
window_pos= 0.442, 0.000
zorder=5

gauge00=G550!G550 00 Overhead Panel,  0,0,980,1042


//--------------------------------------------------------
[Window05]
Background_color=0,0,0
size_mm=1457,297
position=7
visible=0
ident=10031
window_size= 0.759, 0.275
window_pos= 0.063, 0.724
zorder=6

gauge00=G550!G550 00 Standby Background,  0,0,1457,297
gauge01=G550!G550 00 Yaw Damper Panel,  0,0,269,214
gauge02=G550!G550 00 Standby PFD,  468,48,152,152
gauge03=G550!G550 00 Standby MFD,  697,48,152,152
gauge04=G550!G550 00 Gear Lever Panel,  890,14,197,240
gauge05=G550!G550 00 Brake Pressure,  1322,34,97,97


//--------------------------------------------------------
[Window06]
Background_color=0,0,0
size_mm=675,702
position=8
visible=0
ident=THROTTLE_PANEL
window_size= 0.352, 0.650
window_pos= 0.520, 0.370
zorder=7

gauge00=G550!G550 00 Radio,  218,562,239,239
gauge01=G550!G550 00 Throttle Quadrant,  0,0,675,702


//--------------------------------------------------------
[Window07]
Background_color=0,0,10
size_mm=800,670
window_size_ratio=0.760 
position=7
visible=0
ident=GPS_PANEL
window_size= 0.237, 0.310
window_pos= 0.410, 0.600
zorder=8

gauge00=GPSNEW!GPS,  0,0,800,670


//--------------------------------------------------------
[Window08]
Background_color=0,0,0
size_mm=270,512
window_size_ratio=0.796 
position=2
visible=0
ident=10034
window_size= 0.112, 0.378
window_pos= 0.638, 0.622
zorder=9

gauge00=G550!G550 00 Rudder Trim Panel,  0,0,270,512


//--------------------------------------------------------
[Window09]
Background_color=0,0,0
size_mm=354,492
window_size_ratio=1.000 
position=8
visible=0
ident=RADIO_STACK_PANEL
window_size= 0.184, 0.456
window_pos= 0.580, 0.400
zorder=10

gauge00=G550!G550 00 Radio,  0,0,354,492


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



//--------------------------------------------------------
[Vcockpit02]
file=G550upperoverhead.bmp
Background_color=0,0,0
size_mm=1024,1024
visible=1
pixel_size=1024,1024
texture=$upper

gauge00=g550!G550 00 Overhead Panel,  -25,-10,1060,1240


//--------------------------------------------------------
[Vcockpit03]
file=G550Dashandscreens.bmp
Background_color=0,0,0
size_mm=1024,1024
visible=1
pixel_size=1024,1024
texture=$dash

gauge00=g550!G550 00 Autopilot,  -43,-3,1093,227
gauge01=g550!G550 00 Display Control Panel,  0,378,1025,247
gauge02=g550!G550 00 DU1 Synoptic,  -4,637,398,316
gauge03=g550!G550 00 DU2 Synoptic,  401,635,451,317
gauge04=g550!G550 00 DU3 Synoptic,  864,638,294,336


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

gauge00=g550!G550 00 HUD PFD,  2,2,1017,1020



[Color]
Day=255,255,255
Night=223,255,255
Luminous=246,115,119

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

 

[tgibson]

Sorry, I've never created a HUD.

 

[A306capt9]

Sorry, I've never created a HUD.

Its ok. I will experiment with the glass. & how do i stop the CTD?

 

[tgibson]

Start commenting out gauges with // until the crashing stops.

 

[A306capt9]

Start commenting out gauges with // until the crashing stops.

Thanks!! I will do that

 

[A306capt9]

Thanks!! I will do that

I commented out the gauges. Crashing stopped.
These are the gauges that was causing it.

///////gauge01=g550!G550 00 Display Control Panel,  0,378,1025,247
///////gauge02=g550!G550 00 DU1 Synoptic,  3,680,419,339/////
///////gauge03=g550!G550 00 DU2 Synoptic,  451,678,370,331/////
///////gauge04=g550!G550 00 DU3 Synoptic,  851,681,294,336/////

What gauges should I put in place of these ? is there alternate other panel I can use/gauges I can use for the G550 and map the VC to it that I can use ?