Solutions
-
n4gix's post in GNS530 in Duke B60 was marked as the answerYour ident is incorrect. It should be 11013...
//-------------------------------------------------------- [Window01] Background_color=0,0,0 size_mm=937,910 window_size_ratio=1.000 position=7 visible=0 ident=11013 window_size= 0.340, 0.580 window_pos= 0.660, 0.420 zorder=99 gauge00=MPI_GNS!GNS530, 0,0,800,581,1:2:11013 -
n4gix's post in F1 GTN Avionics Package for BE55 and C310 ? was marked as the answerAh, so much wonderful confusion. For the record:
1. C310R has three options:
GTN750 + GNS430 (coming in update soon) GTN750 + GTN650 GTN650 + GTN650 2. B55/E55 has two options:
GTN750 GTN650 + GTN650 If you own the GTN650, you can have two for the price of one, COM1/NAV1 and COM2/NAV2.
-
n4gix's post in Awesome Foursome DC-3 model editing was marked as the answerWithout the actual .gmax or .max source files, it is quite simply not possible to accomplish. Period.
-
n4gix's post in Installing Addons outside root v3 folder was marked as the answerConfiguring 101:
Look in the C:\ProgramData\Lockheed Martin\Prepar3Dv3 folder and... Open the simobjects.cfg file in Notepad.exe (or Notepad++.exe) Carefully copy/paste/edit [Entry.0] and contents to the bottom of the file as shown below Note that in the sample entry I've made, I have created a new set of folders on my D drive:
D:\AddOns\SimObjects\Airplanes
[Entry.9] Title=Default Countermeasures Path=SimObjects\Countermeasures Required=True Active=True [Entry.10] Title=AddOn Airplanes Path=D:\AddOns\SimObjects\Airplanes Required=True Active=True You can also edit the gauges.cfg file to add a new ..\gauges folder:
[Entry.0] Title=Default Gauges Path=Gauges Required=True Active=True [Entry.1] Title=Addon Gauges Path=D:\AddOns\Gauges Required=True Active=True The same thing may also be done to any other remote folders you want to have:
effects.cfg
fonts.cfg
et cetera!
-
n4gix's post in Poll - your first impressions of v3 was marked as the answerThere is a "button" to pre-view results without voting.
-
n4gix's post in DTG: What would you like to see in a new Flight Simulator? was marked as the answerModerator's note to everyone...
Please, when quoting a previous post, trim off all but a sentence or two to maintain continuity. It is completely unnecessary to quote an entire wall of text.
Keep in mind that there are folks who log in with their smart phones!
-
n4gix's post in Has Avsim Been Down All Day 10/6? was marked as the answerThe site suddenly crashed today generating 503 errors (an overflow issue) and continues to stay in that state. I was able to gain access most of the day but can no longer. We are not quite sure what caused the current problem(s) but our technician will be checking out the servers to find and fix the problem. Thank you for your patience.
EDIT:
Chase has successfully fixed the 503 errors temporarily until repairs of the server can be made. He put it in Performance Mode which gives us access to most things on the site.
-
n4gix's post in Moving cockpit graphics to a new screen was marked as the answerUn-docking and moving a 2d (flat) panel is possible, but only if one exists!
Most aircraft these days do not have a 2d panel at all. It is impossible to "move" a 3d virtual cockpit to another monitor, as it is an integral part of the visible model.
-
n4gix's post in Can i play offline fsx steam edition was marked as the answerPMDG will not work in FSX:SE until and unless PMDG release new installers.
-
n4gix's post in Cessna 310, Nav/Strobe Wing Fix was marked as the answerOpen the Cameras.cfg file and add the entry to it...
x:\Users\YourUserName\AppData\Roaming\Microsoft\FSX\Cameras.CFG
-
n4gix's post in FSX 4gb RAM usage? How? was marked as the answerWhat is available and what is used are two different things altogether!
Besides, the issue isn't RAM per se, but rather Virtual Address Space (VAS), which again is an entirely separate issue from physical RAM...
To set your mind at rest however, since you are running FSX (LAA flagged) under Win7 x64 operating system, all the prerequisites have been met.
-
n4gix's post in Getting curious ... was marked as the answerP3Dv2 has precisely the same ATC as P3Dv1 and FSX.
Discussion of one's license option is not permitted at AVSIM. Period.
-
n4gix's post in And the Bottom Line is... was marked as the answerYou do know that L-M offers a very liberal 60 day no-quibbling R E F U N D if you aren't happy. So, tell me again what the risk is?
If you want to see how it runs, buy it, install it, then use it for up to 60 days. If you truly aren't impressed, ask for a refund! :He He:
-
n4gix's post in Will the pro version always be useable? was marked as the answerOnce installed it should run essentially "forever." Of course, should you need to reinstall on new hardware and for whatever reason the activation servers are no longer working...
...but that's as unlikely as MS suddenly going out of business! :lol:
-
n4gix's post in Scenery.cfg location (Windows 7) - clarification requested was marked as the answerWell, that's still quite confusing. It seems a bit pointless to have so many copies of a single file scattered all over the place.
At least I've learned my "one new thing for the day" now though. I can sleep easy... ^_^
-
n4gix's post in WAYPOINT ALERT HSI FLAG was marked as the answerIn that case then, let me repost the XML script the correct way for posterity:
<Element> <Position X="0" Y="200" /> <Select> <Value> (A:sim on ground,bool) ! if{ (A:GPS WP ETE, minutes) 2 < (A:GPS IS ACTIVE WAY POINT,bool) (A:ELECTRICAL AVIONICS BUS VOLTAGE, volts) 10 > and and if{ 1 } els{ 0 } } els{ 0 } </Value> <Case Value="0"> <Image Name="wpt Alert1.bmp" Bright="yes"/> </Case> <Case Value="1"> <Image Name="wpt Alert2.bmp" Bright="yes"/> </Case> </Select> </Element> -
n4gix's post in Need help with fuel selector gauge was marked as the answerYou are missing the "colon" before the index number:
This should be...
(A:Fuel tank selector:1,enum)
-
n4gix's post in Strobe Lights was marked as the answerFrequency of flashing is set IN the .fx file(s) themselves, which are nothing more nor less than simple ASCII text files with an .fx extension.