f16jockey_2
-
Posts
1,429 -
Joined
-
Days Won
1
Content Type
Profiles
Forums
Blogs
Events
vBulletin Articles
News
Downloads
Gallery
Store
Everything posted by f16jockey_2
-
You'll have to the same thing with BOTH b707_b1_t.bmp (nose) and b707_b2_t.bmp (tail), or there will a very noticable difference indeed. The result will become brighter, that's true. Less coloured, I dunno. A matter of taste I guess? Wim
-
Almost there. In DXTBMP make sure everything in the Mipmaps settings is unchecked as shown. The alpha layer should be entirely WHITE, except for some windows (as shown above). Also remember, if you transfer from a DDS in stead of a BMP, you have to flip it before saving. Safest is to export/import from a BMP. Wim
-
Think I found it. "707 Travolta Qantas by Ed Knapp" for CS Legandary 707 [FS9]. Could reproduce the translucent gear bay doors and solved it by replacing the alpha layer in b707_b1_t.bmp and b707_b2_t.bmp. With DXTBMP open the above files from a working texture folder. Export their alpha layers to somewhere you can find them (eg desktop). Then open the same files in the faulty texture folder with DXTBMP, import the previously saved alpha layers and save as BMP DXT3. BEFORE AFTER IMO the purpose and use of the alpha layer has changed from FS9 to FSX. Wim
-
Not the correct link. This is a blue-striped/white tail aircraft. Nothing red as in yr pics. Wim
-
What livery are we talking about? A download link to the texture would be useful, or the site where you got it from. Wim
-
a) in the FS9 texture folder, retain ONLY the below texture files (BMP, or DDS if you decided to convert them) b) add a texture.cfg, with following contents: [fltsim] fallback.1=..\texture fallback.2=..\texture\night fallback.3=..\texture\spec fallback.4=..\texture\bump Wim
-
Just one. Not the 1st time I do this btw. One takes a carrier-based aircraft known to work with the Accel carriers, ex. Dino's Goshawk. Calculate the relative positions (hor+ver) of both launch_bar_pivot and launch_bar_lug vs the nose wheel contact point. In the Viking file, look for the nose wheel contact point, do the inverse math of the above to get both launch points, and done. Wim
-
This basically works (the contactpoints being all in the negative was a bit confusing): [launch_assistance] //Nose Gear //point.0=1, -21.00, 0.00, -7.50, 2000.1, 0, 0.6349, 46.8, 0.8000, 1.5, 0.5100, 10.0, 10.0, 0, 260.0, 260.0 launch_bar_pivot = -19.80, 0.0, -4.37 launch_bar_lug = -20.20, 0.0, -4.43 It may need a bit of tuning to keep the nose wheel down while launching... U does nothing. I arms lauch assist and blast deflector launches Wim
-
There's no initial and no target altitude in your "formula", so it's doomed to be wrong. The rule of thumb is 3 Nm travelled per 1000ft of descent. But for some types of jets I found 4 to 1 more realistic. Take notes of your mistakes, and apply the corrections in yr next flight. Wim
-
Fair enough, point taken. I never use the default flight planner, as the alternatives (Simbrief, LittleNavMap, ...) are so much better. So I never encountered that problem. Wim -
Not true. At least for the part of the GPS I'm using. Wim
-
Slew controls differ from the normal flight controls. You probably cleared them, and need to reassign. Wim
-
Imo the AC is meant to be flown from the Vc, and what you see from the ZD panel is how it’s designed. Some ways to find out: - grab the panel on the border with yr mouse, and move it up. See what it gives. - check the main_background.bmp in yr panel folder with Paint or similar. See how big it actually is. Wim
-
https://www.flightsim.com/vbfs/showthread.php?329588-Sound-Issue&p=2147705#post2147705 Wim
-
??? Great, but the relevance escapes me... Wim
-
In Windows: Go to Control Panel, open "Sound", click on the "Communications" tab at the top. Choose the "Do Nothing" option, and click OK. Wim
-
Could be wrong, but IMO that's for selecting menu options (eg the ATC Menu). Wim
-
CLS 747 textures not appearing in library
f16jockey_2 replied to eggeater's topic in FSX General Discussion
+1 Sound= doesn't matter for the selection screen, but if it points to an invalid entry, you'll have no sound of course. The best and easiest way is to check for differences between the [fltsim.x]-sections that show in the selection and the ones that don't. Wim -
NL-2000 V5 is for P3Dv4+ For FSX NL-2000 V4 is recommended. I use it as well. But not the photoscenery, just the airports. Wim
-
What's odd about that? 17.5 million people live in Chile. Their native tongue is Spanish. Wim
-
Propellers appearing as black discs
f16jockey_2 replied to ac103010's topic in FSX General Discussion
Can be, meanwhile you have no doubt installed FSX SP2 or Acc.Pack. Do as MrZippy suggests, change the propdisk texture. Wim -
I do this one AI aircraft folder at a time. When the troubleshooting has concluded, the panel folder gets deleted. OTOH a) when I'm troubleshooting AI, I don't care about flying b) AI aircraft mostly have very distinguisable "manufacturer" entries, like "FAIB", "AI Aardvark", ... c) AI aircraft would be my only entries with a question mark as thumbnail Wim
-
When I get clueless about AI Aircraft, I tend to add a panel folder to them. That way you'll see them appearing in the Aircraft Selection Screen (or not), thus eliminating certain errors or guiding you to them. Wim
-
IMO, your second user has DX10 preview enabled, the main user not. FSX.cfg is in C:\Users\\AppData\...(etc) so can be different for each user. Wim
-
Before calling the cavalry, did you check if there should be more aircraft at the specific airport at the time you were viewing? I mean according to the AI flightplan, not according to your intuition... AIFP has a function to display what aircraft can be expected at a given airport. Flight Plans -> Timetable. The above example (latest AIG schedule) shows only one Iberia Express aircraft a day at Menorca as well. IMO you're seeing the AI traffic just as it's programmed. Wim
