il88pp

when painting I stick a new thumbnail.jpg in the "texture.XXX" folder I'm working on. Something that stands out. For example a full pink rectangle image. Simple trick to make certain you select the correct aircraft from the "Choose Aircraft" list in Fsx.

try disconnecting all other usb devices. (xbox controller, printer, webcam, etc) try with only yoke and mouse/keyb. or only joystick + mouse keyb.

Maybe he meant 'Mode' As in: DX10 Preview Mode.

The following is what I found when looking this issue up online. I nyself do not have this joystick. ------- As far as I understand, the switch on the back of the throttle is a rocker switch. It always returns to center. It does not work like a keypress, its more like a joystick axis. It is normally used for controlling the rudder. From the Manual for your joystick (found online): Hope that helps.

Try making it a .jpeg less then 490 bytes and a max width & height in pixels.

A model is required for the texture. Two were suggested The first won't work in FSX. (It's a fs2002 model.) The second one that's mentioned, I cannot find that file. I did come across another file. The same plane I think. Same author. Chris Buff. But aircraft now converted to FSX. The texture files in the fsx version seem unchanged. Same filenames. So the amerer-air texture can provably be added. This L188 package has lots of textures already installed. FSX Lockheed L-188 Electra Package by: David Grindele l188_pkg.zip https://www.flightsim.com/vbfs/fslib.php?do=search&fname=l188_pkg.zip

https://www.flightsim.com/vbfs/showthread.php?310382-FSX-Acceleration-disk-problem

I dont see a texture for the KBT version. There is this file in the library. A fs2004 aircraft, but you may get it to work in fsx. FS2004 Aircraft. Name: l188_amerer.zip Size: 1,871,358 Date: 03-10-2015 Downloads: 195 FS2004 Amerer Air Lockheed L188 Electra. Textures for Chris Buff's Lockheed L-188; requires ELEC-CB.ZIP or L188ELECTRA.ZIP.

if you were stood at the runway end looking towards the landing aircraft, and you could see the glideslope signal, you would see it rises 300 ft for every NM (Nautical Mile). Your last fix is 5Nm from the runway. At 5 Nm the glideslope is at a height of 5 × 300 = 1500 ft You said you were around 2300 ft at 5 Nm. And then you waited for lineup before engaging Approach. So when pressin 'App' you were closer then 5Nm, at 2300. You were above the glideslope when engaging Approach.

Adding a bit to my last message. -------------| There are 2 separate commands (keyboard assignments) for viewing ahead. = "eyepoint Reset" that does two things:It resets the view to 'forward' but it also resets the eyepoint (seat position) and zoom level. So if you had moved the eyepoint and changed zoom level in flight then using "" those things will now be reset, and you will have to adjust your eyepoint and zoom level again. A better () command to use is: "Look Forward (3-D Cockpit)" With that command the eyepoint or zoom level stay as they are. This command only resets the view to "Forward". I have "Look Forward (3-D Cockpit)" assigned to a joystick button, and use it all the time. I still have "eyepoint Reset" assigned to . Comes in handy as well but I don't use it nearly as much.

that cant be right. 5 Nm from the runway the glideslope is at 1500 ft.

see this post by mrzippy: https://www.flightsim.com/vbfs/showthread.php?322848-more-crashing-on-launch&p=2112785#post2112785

to test if you have the correct password, install a different browser on your pc. Test on the new browser if you can log in. If it's the wrong password you should still be logged in on your usual browser.

what happens on my phone is: i type the login and password correctly I click the login button. And I get a message: "username or password incorrext, be aware it's case-sensitive" but once I refresh the page, I am logged in. No idea why I keep getting that message each time I log in.

when you google: Garmin G1000 fsx You find many many different G 1000 versions. Some freeware, sone payware, No idea which one you have. Different aircraft start their approach at different altitudes. an example would help flight: from where to where? what aircraft type? (payware?) cruise alt? which IAF? which STAR? etc.

For military airport scenery for FSX, always check MAIW. They have fsx compatible Traffic, and have the Airports for it as well.

would rotate 180 then flip horizontal work? Then again, he says they "come out backwards". So maybe backwards input is no issue and flipping horizontal is not needed. (By the by... I think rotating 180 and flipping horizontal, give sthe same result as flipping vertical without rotating.:confused:)

Texture loading will go much faster from SSD then from Mech-Hdd. Ssd has no moving parts, and has way higher data transfer rate. If you have an old mech drive as C and fsx drive, Save the whole HDD drive, all partition info+data+bootdrive into one system-inage file. Store the image file on a ExternalHDD Unplug power cord. Open pc. Unplug HDD (power+data) Plug in SSD. (pwr+data) Boot pc with bootstick that contains the imaging program. Use imaging program from bootstick to restore your system image to the SSD. Easyest if SSD is same size as HDD, or bigger then HDD. System inaging prograns are available a freeware and open source. Payware programs like Acronis are often given as freebee with a new disk. (So free licence code included with new Ssd or Hdd.)

drivers for old joystick port devices do not and will not work on Win7 On Win7 you will need a usb joystick. The old joystick ports only work in older Windows operating systems. (and perhaps Unix/linux/freeBSD, dunno.). Converters exist, but don't buy. Those can at most make it work as a basic 4-direction and 2-button device.

They are all in the [lights] sction. so fsx sees them all as "lights" (they are not for example in the [smoke] section.) Those original 'lights' are probably controlled by a gauge. (in this aircraft). They are effects like vapor trails that the gauge will switch on and off. (a gauge Showing them only when in air and also above mach 1 for example.) The orinal effects wont show correctly if you renumber those. some, like 6,7,8, and 9 (the numbers you posted in post 6) are switched on and off automatically. by a gauge. Do not change the numbers. if you do the gauge will switch on the wrong ones. add your lights effects at the end. (if not over the max. no. of lights yet.) And no. These lights are not part of the model. they are simple effects. Simple effects you make show 'around' or 'on' the model, simply by adding to the light section of the aircraft.cfg file. As explained, the position you chose for your wing lights was wrong. It was nowhere ​near the wing. use the green or red navlight effect to find the correct location for your taxilight effect. once you find the right spot change it to the shockwave effect you wanted. (or to a default taxilight effect.) (PS: shockwave is payware. if you dont have that installed you will not see any shockwave effects.) (PPS: light effects will not light up the ground.)

confusing. you said there were only a few lights. Now you list a whole bunch. Nevermind. Those original lights are probably controlled by a gauge. They are effects like vapor trails that the gauge will switch on and off. The orinal effects wont show correctly if you renumber those. Wat I meant about fx_navgre: In the line you are trying to add, dont use your fx_shockwave Use fx_navgre instead. 1 - That is a default effect. So that should show up. 2 - It is an effect that is easily visible. Bright, and also visible from all directions. shockwave effects can sometimes be seen from one direction only. They also need to be correctly installed. (You so realise that shockwave effects are payware, yes?)

Tip to make the Trial an error go faster In keyboard assignments, assign a key to: "Aircraft (reload)" View your aircraft. Leave Fsx running. Edit the position of the light in the aircraft.cfg file. Save the aircraft.cfg file. (but leave file open.) Go back to fsx Press your "aircraft reload" -key and see the change. Not good yet? edit aircraft.cfg again save file. reload aircraft. etc... :)

light.10=2, -39.0, -38.0, -2.30, fx_shockwave_strobe_2 , means light 10 type 2 (strobe) position 39 behind 38 to the left and 2.30 below the (0,0,0) point. as all are negative (-39, -38, -2.30) That means point (0,0,0) is in this model defined as located somewhere in the cockpit. Your coordinates are strange. light.18=5, 43.420, 7.50, 0.370, fx_Shockwave_landing_light , is located 43 in front of 7 to the right of and 0.3 above the (0,0,0) point. That's a long way in front of the aircraft. Nowhere near the wing. the same for 7.50 value you picked. That value is too small. Even after moving the light back with the first coordinate, value 7.50 'right' would not be far enough from the middle of the aircraft. The lighteffect would end up inside the aitcraft and be invisible Choose better coordinates. Trial and error. ---------- Also renunber your lights. So: 0, 1, 2, etc. don't start with light.11 Start with light.00 ____________ For now also change light type for your added lights to 3 that way they are operated with the nav-light switch. (which you know works.) light switch gauges in the vc can be problematic. But the nav lights switch usually works.

turn .dds file 180 degrees clockwise. then re-save .dds file. then place in airport. or is it not that straightforward?

Happy to hear that helped. Good thinking to use a different cable. (I hope the power supply holds.;)) Happy Flights!:pilot: