Hi folks,I was hoping someone could help me.

I found a copy of FSPanel Studio at a car boot sale the other day which I bought.

The idea was that I could install FSX compatible gauges in panels of earlier aircraft that otherwise work in FSX. I have successfully re-gauged the Alphasim Whitley (the more observant of you might notice a link between my user name and this particular aeroplane), but I have run into a problem.

I am having difficulty in finding gauges that are suitable for some of the panels, but other than downloading masses of aircraft I don't particularly want just to extract gauges that may or may not even be part of the download.

So the is there a hoard of gauges anywhere that I could download and store. I can't find any of the type of gauges I am looking for, most of the gauges in the download sections of Flight Sim sites like this one have one off gauges like the hover gauges etc, not period gauges or turboprop, jet etc gauges.

Depends what you want this for. If it's purely for your own use you can use any gauges you wish. The gauges on British WWII aircraft were pretty standard so the FS9 default gauges will do for the blind-flying instruments. For the twin-engine gauges what you need is a true- FSX aircraft of a similar type & period to the Whitley. I can think of at least a couple of examples. You can then use the gauges from that.

Of course, if you intend uploading the finished article for others to use you would need permission from the authors of the gauges before doing so.

Quote:

Not sure what you mean by "seed" page.

whitley wrote on Mar 31^st, 2011 at 4:56pm:

Sorry. I know very little about turboprops. I can only suggest the latest FSX offerings from Jens B. Kristensen.

PS. The 2D panels on Rick Piper's Dart Herald & Viscount work fine in FSX. The gauges look pretty good to me.

This is Rick's Viscount panel.


Compare it with the real aircraft. http://www.airliners.net/photo/Vickers-Viscount-(simulator)/0503314/L/

You're not likely to find what you're looking for in one download. My best suggestion is to collect the types of gauges you want to use. The cluster gauges included with some 3rd party aircraft contain a selection of gauges suitable for specific types/periods.

Quote:

Not sure what you mean about removing gauges from BMPs. The gauges used on specific panels are defined in Panel.cfg. FS Panel Studio should do that when you save changes. Did you mean FSX.cfg?

whitley wrote on Apr 4^th, 2011 at 4:15am:

If you replace a gauge rather than adding an extra one FS Panel Studio should update Panel.cfg accordingly* when you save changes. I don't think the version will matter. If yours reads gauges in XML & DLL format then it's fully FSX-compatible.

*PS. You would need to replace incompatible gauges in all windows including the VC which I know you don't use. Alternatively you could simply remove the VC windows.

PPS. Quote:

The easiest way over this is to install gauges of third party aircraft to their respective Panel folders. FS Panel Studio can still read them in this location. This makes it simple to identify & remove incompatible gauges if necessary. You can transfer the compatible gauges to FSX\Gauges later if you wish.

whitley wrote on Apr 4^th, 2011 at 8:16am:

That's not right. FS Panel Studio should do the work for you. That's the whole point of it. I suspect you're adding extra gauges rather than replacing the existing ones.

Before going any further I suggest removing all incompatible gauges from your FSX\Gauges directory. This will make modifying panels much easier in the end. If you want to know what these gauges look like you can always create a dummy Panel folder in the aircraft & paste the FS98-style GAU files into it along with copies of the appropriate Panel.cfg &  BMPs. Name the folder anything you like & open Panel.cfg direct from FS Panel Studio. The incompatible gauges will be hidden from FSX but FSPS will  be able to read them.

Note: I only have the FS Panel Studio Demo version but I've been using its older brother CfgEdit since it was first released in 1999. Both work on exactly the same principles.

When swapping a gauge, the gauge entry in the panel cfg gets overwritten, but that isn't what I was talking about.

I was perhaps replacing some gauges in a non recommenned way by simply selecting the gauge I wanted to try and dragged and dropped it into the vacant space in the bmp. Doing it that way the old gauge entry remained in the panel cfg as well as adding the new gauge. It is all part of the learning curve.

I wonder if I might join in here and ask if it is possible (or perhaps "not too difficult" would be a better choice of words) to create an FS Panel Studio BMP style gauge panel to replace one that is currently all XML?

I have found one of my all time favorite planes to be the DeHavilland Hornet. Great plane! But its gauge panel is pretty much non-readable from any kind of distance. They are all fuzzy.

(The only exception is in dusk or night viewing, where its cool blue backlighting is VERY nice - but I prefer to fly in the daylight.)

The DeHavilland Vampire I downloaded along with it has a very similar cockpit and gauge panel (except with gauges for a jet) and they are "crystal clear" to read. But.......both planes use XML gauges, and I have no clue how to work with those. FS Panel Studio can't even view them (I have tried - I get just a blank black background).

I read the FS Panel manual and even researched online, only to find a statement to the effect that "very little information has been released by Microsoft on XML gauge creation". So if I can't edit the Hornet, I was wondering if I could simply create my own panel in place of the one it has, using FS Panel Studio?

Or is there a similar tool which can edit XML panels?

Thanks for the reply!

I'm on my smartphone at the moment, so I'll check that name when I get back to my PC and can open the files, but I can agree they do not have 2D panels. That creator name looks familiar, so we are probably talking about the same planes.  (Edit - Yes, they are by Robert Richardson in 2010).

I never fly other than VC. The only reason I sometimes use 2D panels is during pre-flight when I can't find something in the VC (for example, the GPS/Nav switch) or sometimes to access autopilot or radio settings before departing. So creating a 2D panel would not solve the problem for me. If the VC of the Hornet is defined within its model files then my next question is - can I edit those? Is there a utility or program available which I could use to make the changes?

In the description of the Hornet, he mentions adding "reflective glass" on the gauges. Although perhaps that makes for nice realism, I'll bet it is the cause of my problem. I have noticed that on the rare ocassion when the lighting happens to be "just right" I can read them much more easily. If that is the cause, I'd like to "undo" that feature if possible. Perhaps doing so would only involve minor changes to the code in the model files. I have edited configuration files several times, so I am certainly willing to try if I can learn how a model file can be modified.

I don't recall a mention of reflective glass on the gauges of the Vampire. That's why I am inclined to think the above. Perhaps I could even compare the code between both planes to look for differences.

Thanks for looking into this for me. Since, as you say, the tools and knowledge to use them would likely require significant effort on my part, yet your test results yielded little change, I don't see value in pursuing it further. I did more research on the subject, this time including model files and their makeup, and ran across what I believe may be the reasons the Hornet gauges are so blurry.

The first thing I read was on this forum where members were discussing panel creation and the resolution settings coded into the VC section of the panel configuration files in the , and how increasing those numbers can produce higher clarity gauge imagery. However, those numbers do not appear in the Hornet panel.cfg at all. I tried adding them but no change in result.

The next thing I read was discussing the source imagery for gauges, and how crucial it is to have high resolution pictures of the correct initial size, becuase the MDL file creation process compresses and resizes them to fit the panel area being built. I am guessing that for whatever reason, he did not have access to good photos of the Hornet gauges, and so the end result magnifies the lack of initial clarity. I found other subsequent variations the same author released of the Hornet, and in all cases the same fuzzy gauges were used. So it might simply have been the best he had to work with. What puzzles me in the end is why the gauges he put in the Vampire, which are so similar, are so clear. I think I would have been trying to utilze those that are the same in both planes, and tried to create from scratch any that were different, with the same clarity. But that's just me I guess.

Add to all this the fact that designers generally don't like modifications being made to their creation, and I ended up looking for a suitable replacement for the Hornet last night. So far I haven't found anything with twin engines and that kind of performance short of jet aircraft, which also happens to look as nice and fly as smoothly as his Hornet does.

I initially fell in love with the P51 offered in FSX Acceleration simply because it is crazy-powerful and smooth as butter, even at high altitudes. So I went looking for a plane with 2 of those lovely Merlin engines, and that was how I learned of the Hornet. If you can suggest any other twin engine planes (I like how they sound) with similar features of smooth flight control, nice graphics, and cruising speeds apporaching 500 knots I would like to check them out. The Hornet is one fine plane, by me, and will be hard to replace. So I'll keep it even though I can't read the compass at all when in flight. (GPS or the HUD display, which I am sure it didn't have, work in place of the compass).

Thanks!

Thanks. I had that thought at one point, but like you mentioned it is freeware, so he may not want to re-visit the project. I'll see if I can find a way to contact him. Can't hurt to ask nicely, right?

I don't recall if I mentioned it here, but one clarity issue I sometimes get is caused by my using a triple display setup for FSX. Spanning 3840 x 1024 sometimes exacerbates when part of the aircraft isn't clear at the start, especially small gauges.

I have the same issue with the FSXA EH101 panel, in that they are so small in the VC I can't read them when zoomed out to get decent visibility of the scenery. For that I modified the panel.cfg so a window of the 2D Main Panel is the size I want and positioned over the VC panel's rendition of those tiny gauges. But the 101 has a lot of blank area on its VC panel, so I am not covering anything crucial when doing that. The VC panel in the Hornet doesn't really have the room to do that, and it also has no 2D panels to work with anyway.

Thanks for the help!