f16jockey_2
-
Posts
1,431 -
Joined
-
Days Won
1
Content Type
Profiles
Forums
Blogs
Events
vBulletin Articles
News
Downloads
Gallery
Store
Posts posted by f16jockey_2
-
-
fsxwikdw.zip shows on my FSX Accel Boxed without problems.
Could have two reasons (or a combination of both):
a) I have the "VCRainFix textures" installed since I don't know when
b) I'm running DX10 preview with Steve's Fixer.
Wim
-
... or is this a modeling issue that I can't fix & will just have to live with it?
It is. Cannot be fixed.
IIRC unloading SP2 (or Accel) would visually solve this, but that's hardly an option IMO :rolleyes:.
Wim
-
The airline and aircraft callsigns list in the link are the DEFAULT ones.
My airlines.cfg has 4858(!) entries, most of them added by EditVoicePack.
Same can be said about the aircraft types.
BTW the thread is about parking codes.
This is what the FSX Accel SDK Help file says:
So as I said previously, you can put anything in there, as long as the entry in aircraft.cfg and in the AFCAD match. In MAIW packages for example, you'll find entries like "VX50", "VFA103" etc.
Not ICAO, but they work.
Wim
-
There is no such list. Means you can use whatever you like in atc_parking_codes=XXX.
When landing somewhere, default ATC will search the AFCAD for a match, and try to send you down there.
So all you need to do is add the XXX Code to the appropriate parking spots on ALL AFCADs you plan to fly to (or you plan to send AI traffic to).
Wim
-
Try p-3b_aew_fsx.zip in the Avsim library (no idea how set up a link to it, sorry).
[EDIT]It’s here in the library as well, same filename.
Wim
-
Support for some types of gauges was discontinued from FS2004 to FSX.
Surely you must have received some on-screen warnings when loading the AC in FSX the first time?
Can be fixed by replacing the discontinued gauges with newer ones.
Download name/link?
Wim
-
I think you were close to OOM.
Lower some of the settings and do the same flight again?
Wim
-
Where is your FSX located?
If you've actually installed FSX in C:\Program Files (x86)\... (the default location) then it might be necessary to either run EVPX "As Administrator" or to temporarily disable Windows UAC (updating the Voicepack isn't something you'd be doing every day IMO).
I cannot test this myself, as my FSX is located somewhere else.
Wim
-
Correct link to Airport Design Editor:
http://www.scruffyduck.org/airport-design-editor/4584106799
Wim
-
The older versions of EditVoicePack are still free and will do the job.
https://editvoicepack.com/try-and-buy/download-old-versions/
You need version 4.0
Wim
-
To install an MAIW package.
First, create an empty dummy folder (in my case F:\Aircraft Install).
Run the MAIW Installer and point it to yr newly created folder.
Upon completion, the installer created an FS9-lookalike subfolder structure (outlined in green).
The BLUE entries should be copy/pasted into yr FSX install, but with the following restrictions:
- the contents of the Aircraft folder go to
\Simobjects\Airplanes (in this case it's one folder, for other packages there could be more) - the BGL in Scenery\World\Scenery goes to the same location in FSX, but needs to be converted to FSX format (for the known reasons, which I won't re-explain here)
The YELLOW entry should be handled with care, some know-how is needed.
Some of the files are waypoints, and are required.
Some of the files are auxiliary for the red entry, and should be omitted.
In this case I'd only transfer the 3 files ending on RND.bgl (didn't test).
The RED entry should be handled with EXTREME CARE. It's an FS9 AFCAD. Could work in FSX, could not.
Enough info on how to get MAIW scenery working in FSX can be found on the wwweb.
Or find/download/install an already updated FSX AFCAD (for KSKF in this case).
You can compile and recompile the source txt files as much and as long as you like, without installing the supplied aircraft you'll see nothing. And in most cases an updated AFCAD is also needed.
Wim
-
-
An aircraft #2, registered RJBB departs Osaka on Sunday 15:07, flies to KLAX at FL360 to land on Monday 01:54. Departs KLAX on Tuesday 04:00 back to Osaka (FL360 again) to land there on Tuesday 14:47.
It does it once a week, will be visible with traffic set at 1% or higher. And probably something I've overlooked.
[EDIT]
R means it'll be called by ATC by the registration (RJBB), not by an eventual Airline annex flight number (the 0001 and 0000)
Not sure, but the times are Zulu IMO.
It's read from left to right.
Wim
-
I’ve located and installed the complete OZx package on the ORBX forums just last week.
Wanted it for some reason.
There’s quite some downloading and installing involved, as all needs to be done incrementally.
In this thread KGRB is mentioned to be part of OZx 3.5 (included in the above link).
Funny thing is you started that thread yourself??? So why am I even telling this?
Anyway, I’ll check Green Bay once I’ve completed my current flight.
Wim
-
Never mind. Found a pretty simple solution with a counter.
ISG FMS Control for Captain Sim 1011 ISG_Control_CS1011.xml True 0.000,0.000 <br /> (L:count,enum) 7 >= <!-- Check every nth time --><br /> if{ 0 (>L:count,enum) <!-- Reset counter --><br /> (L:isg_lnav,bool)<br /> if{ (A:HEADING INDICATOR,degrees) near (L:isg_lnav_hdg_set) != <br /> if{ (L:isg_lnav_hdg_set) (>K:HEADING_BUG_SET) } } }<br /> els{ (L:count,enum) ++ (>L:count,enum) } <!-- Increment counter --><br /> <br />Wim
-
I made a background gauge to make the Captain Sim L-1011 work with ISG gauges FMS flightplan.
It's loosely based on a gauge from Paul Tally for the CS-737 I found at Avsim.
Here's the code:
ISG FMS Control for Captain Sim 1011 ISG_Control_CS1011.xml True 0.000,0.000 <br /> <br /> [color=#a52a2a] (L:isg_lnav,bool)<br /> if{ (A:HEADING INDICATOR,degrees) near (L:isg_lnav_hdg_set) != <br /> if{ (L:isg_lnav_hdg_set) (>K:HEADING_BUG_SET) } }<br /> <br /> [/color]Basically it reads two variables from ISG:
L:isg_lnav detects if the LNAV button is active or not
L:isg_lnav_hdg_set is the heading the FMS wants the AC to follow
So when needed, the gauge injects L:isg_lnav_hdg_set into A:HEADING INDICATOR via >K:HEADING_BUG_SET
Meaning with AP HDG and LNAV active, the aircraft follows the FMS flightplan. Hurray!
Using the gauge, I observed the following:
when the gauge is refreshing A:HEADING INDICATOR constantly (when the AC is turning) it puts a high load on the system, making other gauges lag.
For example the altitude selector changes in increments of 1000 where normallly it's 100. The IAS selector changes in increments of 10 where it should be 1. IIRC that's proof of the gauge refreshing too fast. When flying straight, all mentioned selectors work OK.
So my question is: how do I diminish the load from the above gauge? Maybe a timer, maybe something else?
Any suggestion is welcome. And code would be appreciated, as I'm a very casual programmer.
Wim
-
Do you actually manage to let the AI land on the stern (the wires) and take off from the bow cats?
Or maybe using another type of carrier than the US angled runway type?
This is/was a finished chapter for me, but I’m starting to feel some kind of itch...
Wim
-
I have compared both aircraft.cfg files with each other...
Wrong spot. Engine startup is defined by gauges. So rather check the panel.cfg files.
Wim
-
On my sim there's ILS/DME Rwy 27 (IGOS) 109.95 MHz. 265°/GS 3.5°
As I regulary do navaid updates, I'm not sure if it's default or not.
Wim
-
... all this utter crap ...
???
Couldn’t we just keep our comments to “The scenery serves it’s purpose for online pilots, but is not suitable for AIâ€.
Wim
-
Plus there's also a site with Finnish scenery, but I don't seem to have the URL.
This one?
http://fisd.fsnordic.net/projects/
Wim
-
While you’re in Scandinavia, you might check out this one as well:
https://www.flightsimnorway.com/addons/default.php?funct=dl&pack=aon
Wim
-
Downloaded the package, opened a random airport from it and ran the ADE fault finder.
As I predicted in my above post. Not eager to correct this, sorry.
Wim
-
The scenery is made by/for VATSIM simmers.
My experience with those sceneries is they’re visually extremely correct with regards to taxiways, signs, frequencies etc. All according to the latest charts. But obviously they don’t care about AI.
So expect unconnected taxiways, unconnected parking spots, unconnected whatevers, as long as it’s visually correct. In other words, lots of work to make it AI ready.
A VATSIM afcad is not the easiest one to start from for a beginner.
Wim
Fresh FSX Install - Order Of Addon Installation
in FSX General Discussion
Posted
In my personal opinion, the installation order doesn't matter.
What's important is the ultimate order of the scenery entries in scenery.cfg, to make some packages overrule others in the way they should.
A good document to read is https://flightsimeindhoven.com/2017/07/23/scenery-config-editor-in-practice/
It encourages to use SceneryConfigEditor (links in the above web page).
That said, this is how I would do it.
First : FreeMeshX. Install following their instructions and put their folders just above 1107 Base
Then: ORBX Global, followed by the 2 FTX regional packages and what's left of ORBX.
In FTX Central Settings, choose a correct Library Entry Point. IMO it should be just above the Accel Cities, just above Las Vegas.
Then, what's left, the other addon airports in no matter what order, and finally GSX.
Be aware: some airport addons can have multiple scenery entries.
If not automatic, they sould be added to the scenery database in the correct order. Follow the developer's destructions.
Let FSX rebuild the scenery on regular basis, and do tests with every step.
I skipped UTX, as I have no idea how UTX interacts with ORBX. Others may drop in on how to make them work together.
IMO Holgermesh PNG can be skipped when using FreeMeshX (but again, that's my opinion).
Wim