phillroath

I gave you a howto on your post on flightsim forums.http://forums.flightsim.com/vbfs/showthread.php?t=181830Phill

The flaps appear to be correct. The Maule has one notch of negative flap setting for cruise conditions. When first coming out, TailDragger of ACES blogged about this. That data may still be there.Phill

My apologies, Bill. I was not trying to do any selective quoting (that's why I made sure the link was there for folks to read the whole thing). That was just the part that got me.I seem to have more difficulty expressing myself on the internet, but not in person. Perhaps body language has something to do with that.The point was that one should not have to prove to anyone in advance that they are not up to no good. (edit: is this a triple negative?)Have a nice day.PhillPS - tubeliners? That's a new one on me. Have no idea what that is. : ) Edit2: Now I know what a tubeliner is thanks to google. I thought I was being called a name, but now just see Bill does not care for airliners. Funny how we can read something wrong.

Actually, I did tell the whole story. The messages above was what got me, an attitude of "Prove to me in advance you're not whatever."Yes other sites will boot someone for harassment or whatever and they should. But most other sites let you in with registration and if they have a warning about misconduct, that's OK to. I've been going to and fro on this planet for some seven decades and I always try to treat others with respect. I expect the same.I do know this company, I've had several of the earlier FS9 737 aircraft and really enjoyed them. I'm not putting down their product, just some of the attitude they exhibit. You also said, "They are saying that they don't want spammers, harassers, or solicitors. Are you planning on spamming their website or selling another developers product on their website, or just getting on and flaming them? If not, you have nothing to worry about. There won't be any problem."I've seen times and places where some used the "you have nothing to worry about" statement to get things passed (speaking of legislation) that did have other consequences. So, no, I won't try to answer their questions in order to prove something. That's just me being stubborn. Anyone should be allowed to view (not post) for someone who is interested in a product. Anyhow, got to get back to what I was doing. Enjoyed talking to you. Have a nice day.Phill

Well, I went to your link to see the screen shots and found you have to register and when reading the regristration pages found they were ready to threaten a potential customer. And here's a direct quote from their website..."Failure to adhere to this will not only result in banning of your IP from this forum, but prosecution under the laws effective for the United States for harassment, as well as violation of EULA for forum registration."That's located at - http://www.arianeaircraft.havetofly.com/viewtopic.php?t=270So when I read that, I said, "No thanks. Won't deal with a company like that."Phill

Could be your logbook and there is a utility to fix that. Try this...http://library.avsim.net/esearch.php?DLID=...hor=&CatID=rootPhill

I just now loaded the Maule to make sure if I remembered it correctly. It's not just you, the model has a funny in it. If you look at the panel switches themselves, you will see "L" does all three light switches, and "Cntl-L" only switches the landing light.Now go to spot view (which is what I believe you're talking about) and you will see the landing light is linked to the model navigation lights. Red on the right wing, green on the left wing, and white on the tail. These are on regardless of whether the nav switch is on or off. Now when the "L" command switches all on, the built in nav lights come on and also the lights from the lights section. I kept getting confused until I went through the exercise shown above. So you're not having a problem by yourself. The model has the navigation lights built into the model linked to the landing light, plus the lights from the lights section.PhillPS - I have acceleration so do not know what pre-SP2 behavior is like.

Search the forums for Overland. I do not have them, but several threads mentioned that Overland has a patch for FSX, but their aircraft apparently do not work with DX10 preview turned on.If you're running Vista and have the DX10 turned on, try turning it off.Phill

There is a quick thing to try. Go to: Settings - Customize - GraphicsOn that panel move the Global Texture Resolution slider to Very High. This has solved blurry VC for lots of folks. If it don't work for you, no harm done in the attempt.Phill

>Could you please explain how to change the values for other>airplanes?Here are the ones I've done so far.This shows how one user gets daytime VC lights and retains the night VC lights. After inserting the smokesystem (and make sure the VC lights are commented out under the LIGHTS section), then by using the "i" key in the daytime you get good VC lights. At night the Shift-L controls panel lights but both on are super bright, so just toggle the "i" key again to use only the night system. This way you get the best of both worlds. These are the six aircraft I've done this for.Goose Gruman, C206B Grand Caravan, Default B737-800, Default C172, Default Douglas DC3, and Maule M7 260C=============== Goose Gruman =====================[Views]eyepoint = -0.9, -1.35, 2.95 //Longitudinal, Lateral, Vertical (feet)[SMOKESYSTEM]smoke.0 = -0.9, -1.35, 2.95, fx_vclighth //Add vc lights for day use[LIGHTS]//Types: 1=beacon, 2=strobe, 3=navigation, 4=cockpit, 5=landinglight.5 = 1, -15.6, -0.26, 4.4, fx_beacon ,//light.7 = 4, 1.60, 0.00, 2.70, fx_vclight,================== C206B Grand Caravan =======================[Views]eyepoint = -12.5, -1.2, 2.19 //(feet) longitudinal, lateral, vertical distance from reference datum[SMOKESYSTEM]//smoke.0 = -10.5, 0.00, 1.19, fx_vclighth //Add vc lights for day usesmoke.0 = -12.5, -1.2, 2.19, fx_vclighth //Add vc lights for day use[LIGHTS]//Types: 1=beacon, 2=strobe, 3=navigation, 4=cockpit light.0 = 3, -16.72, -25.80, 3.85, fx_navredhlight.1 = 3, -16.28, 25.80, 3.85, fx_navgrehlight.2 = 3, -42.28, 0.00, 2.12, fx_navwhihlight.3 = 2, -16.90, -25.90, 3.85, fx_strobehlight.4 = 2, -16.45, 25.90, 3.85, fx_strobehlight.5 = 1, -40.10, 0.00, 10.01, fx_beaconh//light.6 = 4, -11.61, 0.00, 0.98, fx_vclight================ Default B737-800 =========================[Views]//eyepoint = 48.2, -1.55, 1.9 //(feet) longitudinal, lateral, vertical distance from reference datumeyepoint = 48.2, -1.20, 1.9[SMOKESYSTEM]//smoke.0 = 47.60, 0.00, 3.00, fx_vclighth //Add vc lights for day usesmoke.0 = 48.2, 0.00, 1.9, fx_vclighth //Add vc lights for day use[LIGHTS] //Types: 1=beacon, 2=strobe, 3=navigation, 4=cockpit, 5=landinglight.0 = 3, -24.20, -56.60, 3.90, fx_navredm ,light.1 = 3, -24.20, 56.60, 3.90, fx_navgrem ,light.2 = 2, -71.32, 0.00, 5.92, fx_strobeh ,light.3 = 2, -25.00, -57.20, 4.20, fx_strobe ,light.4 = 2, -25.00, 57.20, 4.20, fx_strobe ,light.5 = 2, -7.55, 0.00, -5.50, fx_beaconb ,light.6 = 1, 2.00, 0.00, 8.70, fx_beaconh ,//light.7 = 4, 47.60, 0.00, 3.00, fx_vclighth ,light.8 = 3, -29.50, -56.60, 3.70, fx_navwhih ,light.9 = 3, -29.50, 56.60, 3.70, fx_navwhih ,================= Default C172 =====================[Views]eyepoint= -3.95, -0.85, 1.9 //(feet) longitudinal, lateral, vertical distance from reference datum[SMOKESYSTEM]smoke.0 = -2.27, 0.00, 1.45, fx_vclighth //Add vc lights for day use[LIGHTS]//Types: 1=beacon, 2=strobe, 3=navigation, 4=cockpitlight.0 = 3, -2.76, -18.11, 2.97, fx_navredlight.1 = 3, -2.78, 18.11, 2.95, fx_navgrelight.2 = 2, -3.13, -18.31, 2.95, fx_strobelight.3 = 2, -3.11, 18.31, 2.95, fx_strobelight.4 = 1, -20.51, 0.00, 6.20, fx_beacon//light.5 = 4, -2.27, 0.00, 1.45, fx_vclight=================== Default Douglas DC3 ======================[Views]eyepoint = -6.495, -0.8, 3.25 //was 3.32//eyepoint = -6.495, -1.4, 3.26 //-6.495, -0.8, 3.25[SMOKESYSTEM]smoke.0 = -6.50, 0.00, 4.80, fx_vclighth //Add vc lights for day use[LIGHTS]//Types: 1=beacon, 2=strobe, 3=navigation, 4=cockpit, 5=landinglight.0 = 3, -27.20, -46.30, 0.65, fx_navredm ,light.1 = 3, -27.20, 46.30, 0.65, fx_navgrem ,light.2 = 3, -64.00, 0.00, 2.72, fx_navwhi ,light.3 = 1, -36.80, 0.00, 6.25, fx_beaconh ,//light.4 = 4, -6.50, 0.00, 4.80, fx_vclighth,light.5 = 4, -33.00, 0.00, 4.20, fx_vclighth,==================== Maule M7 260C ===========================[Views]eyepoint= -2.0, -0.75, 1.4 //(feet) longitudinal, lateral, vertical distance from reference datum[SMOKESYSTEM]smoke.0 = -2.24, 0.00, 2.20, fx_vclighth //Add vc lights for day use[LIGHTS]//Types: 1=beacon, 2=strobe, 3=navigation, 4=cockpit light.0 = 3, -1.23, -16.56, 2.68, fx_navredlight.1 = 3, -1.23, 16.56, 2.68, fx_navgrelight.2 = 3, -17.05, 0.00, 4.45, fx_navwhilight.3 = 2, -1.23, -16.56, 2.68, fx_strobelight.4 = 2, -1.23, 16.56, 2.68, fx_strobe//light.5 = 4, -2.24, 0.00, 2.20, fx_vclight

>Hey Bill, my problem with lighting is in the goose v/c. I>can't see the gauges very well in the daytime. Is there a way>to fix that in the goose config?This is not as fancy as Bill's solution, but I fixed it by using the smoke system and by changing the location of the vclight. Here is what I wound up with (I moved the EYEPOINT, SMOKESYSTEM, and LIGHTS all to the same place in the Goose aircraft.cfg file) and did this...[Views]eyepoint = -0.9, -1.35, 2.95 //Longitudinal, Lateral, Vertical (feet)[SMOKESYSTEM]smoke.0 = -0.9, -1.35, 2.95, fx_vclighth //Add vc lights for day use[LIGHTS]//Types: 1=beacon, 2=strobe, 3=navigation, 4=cockpit, 5=landinglight.5 = 1, -15.6, -0.26, 4.4, fx_beacon ,//light.7 = 4, 1.60, 0.00, 2.70, fx_vclight,For daytime, press the "i" key for smoke and get your panel lit up. Then at night, "i" key to turn this off and use the FSX night lights. This was (I think) an offshoot of FSX SP2.Phill

In addition to what fsxmissionguy said, these hangs are in usually full screen mode. I just hit alt-Enter to go to windowed, do my menu activities, then alt-Enter again to go back full screen.YMMVPhill

Just did a google with g2d.dll and found lots of hits and not just for FSX. For example, here is one suggested fix...http://forums.simradar.com/g2d.dll_error_-...ash_P93350.htmlPhill

I had something like that and then (after reading on the forums) went to my nVidea control center and forced VSYNC to on and it fixed it. Simple to try and beats complete re-installs. :-lol Phill

You've probably already done this, but everytime I had those exact symptoms, Pitot Heat solved it. In some cases the acft switch did not seem to work, so I use the keyboard.Pitot Heat = Shift HOf course that's the default settings, did you reasign any controls?Phill

>Will this method work on the instrument panel in the Grumman>Goose? I like to fly this plane but the gauges are very hard>to see unless it is nighttime.>>DonYes - just tried it for C172, DC3, and Goose. The Goose was interesting because it did not help like the others until I moved the vclight to the eye viewpoint and it works great there. In the attached file are the aircraft.cfg changes for all three aircraft.PhillEdit to emphasize - when night lights become active, turn off these lights ("i" key) or it's too bright!

Just thought I'd pass along a method I came up with concerning VC lights. Probably many have already done this, so if this is old news just ignore. Since XPack (with SP2) the VC lights section was commented out which means during the daylight the gauges can be very hard to read. But if you add them back in, then at night everything is super bright and hard to see outside. I wanted both and here's what I did.I added a smoke section in the aircraft.cfg and pointed that to the vclight fx file. Attached is an image of the added smoke section just above the lights section. Note the lights are still commented out, but now during the day, pressing the "i" key turns on the lights. Then at dusk when the night textures come out and it's too bright, hit the "i" key again and they're back to normal. The attached image is of the default 737 and I've also done it on the Maule. Note there is no light number under smoke, only the x-y-z locations. Obviously, this only works on aircraft that do not use the smoke section.Phillhttp://forums.avsim.net/user_files/184805.jpg

I know this is too late to help you, there is a utility called FS_TRU in the downloads section. The TRU stands for Texture Replacement Utility and always makes backups so you can restore the original. Nice utility and I've used it several times and have had occasion to restore the originals.For future reference, you might want to get this.Phillhttp://library.avsim.net/esearch.php?CatID...util&DLID=95916

I feel the same. The change for me came with my purchase of the Shockwave Solo P-51 (in FS9). Since then, I reject acft without a VC. My two favorites right now are the Realair SF260 and the Acceleration F-18.PhillEdit to add P-51 was in FS9.

I have FSX with Acceleration and have not seen this. Which aircraft? Is it an fs9 with flex wings? Probably no help from me but if you identify the aircraft, someone that has it might be able to help.Phill

>You are right, there is no nose wheel steering in the CFG>file. Acrtually there is. Look under CONTACTS and see thispoint.0=1, -18.00, 0.00, -6.60, 1600, 0, 0.6349, 75.0, 0.2000, 3.5, 0.6100, 3.0, 3.0, 0, 0.0, 0.0The seventh parameter is steering angle in degrees. In this case the nose wheel turns 75.0 degrees. The original OP was talking about the turning on landing. I had it also and disabled the line under BRAKES section..//differential_braking_scale = 1.0I use a twist stick (no rudder pedals) and this seemed to work for me. Still takes care but by not turning the stick I can apply brakes and be ready to release them the moment a yaw starts to show.Phill

Along with the other response you got, Shift-F10 brings up the knee board and one of the options shows all the keyboard actions. No pausing the sim or anything, just open and scroll to the section you're interested in.Phill

2D view bitmaps do not display in FSX. To get a cockpit view, the model needs a VC. I don't fly anything now that does not have a quality VC (e.g. - RealAir SF260 or Acceleration FA-18).Phill

>>2) add-ons made with the FSX SDK work properly. The RealAir>SF260, LevelD 767 and PMDG 744X are all examples, as well as>Ultimate Terrain X works. Some are a mixed-bag, such as>MyTraffic X, with some of the AI planes being FS9 planes.>Add to this list the Shockwave Curtiss P-40 works for me under XP and DX9 with FSX Acceleration/SP2.Phill

Just a wild guess, but the registry may be messed up and Flight 1 has a free download for that. Go here (second link down).http://www.flight1.com/view.asp?page=libraryIf it doesn't help, no harm done.Phill