Andydigital

The Linda site does have a tendency to be very unreliable, I have a few alternate links for some downloads stored in my Dropbox. See the post below for details. http://forum.avsim.net/topic/338310-linda-v111-released/?p=2714370 Also my Anti virus software always blocks some of the images shown in that thread (in the first post) as it doesn't trust the zenfoto.ru website the images are supplied from.

Likely its picking up a string in the name that is the same for both modules, 737 probably. As far as I remember the Magenta module came much later compared to the others and probably hasn't been tested by Artem because he doesn't have PM avionics.

Simply delete or move out the folders that reference Project Magenta and all should work OK then.

Copy and paste the above code in post #14 into the file called mjc8q400.MCRO (replacing the whole contents of the file) which is located in the Modules folder inside your main FSX folder. Open the mjc8q400.MCRO file with Notepad, do not use a normal word processor as it will insert invisible formatting into the file which will break it.

You wouldn't believe it but my Maximus 6 Extreme battery died after a week of use too, its ridiculous considering I paid over £300 for the bloody thing, I had the exact same thing happen to me a couple of days ago with the clock, lol, I spent about 2 hours trying to figure out what the hell was happening :lol:

Hi David, If you look on the label on the little black power supplies that VRi send with the hardware you will see that it says 100-240v on the them, that is the range of the input voltage they will accept.

Yes it is possible, but you need to edit the panel.cfg for the aircraft in question and add the below line to the panel you want to keep open. Type=Special Now I am working from memory here and I don't have access to FSX as I am in the middle of a new PC build, so I'd recommend a search here at the forum for that line above just to confirm it. I have answered this question here before I think so it may be worthwhile using the advanced search function with my username as well as the above line to see if I remembered correctly, lol. Edit: Never mind I found it; http://forum.avsim.net/topic/347595-any-way-of-keeping-2d-panel-popups-in-place-in-a-view/?hl=+type#entry2099434

PTPP bought!! Charles thanks for reminding me about this facility from Intel, at only $25 for a 4770K it is great peace of mind for overclockers.

I think FSUIPC may have facilities built in to see the PFC buttons but I dont think LINDA accounts for this as FSUIPC uses a special driver that Pete wrote, I maybe wrong though so you will need to check elsewhere. As for your other jetmax issue, no idea, but try it through FSX directly to see if you have any problems there too.

Can you assign the buttons directly in FSX via its control menu? If not then you probably won't be able to in Linda either, hence why its greyed out because it has no assignable buttons. If you can assign buttons directly in FS then I have no idea why its not working in Linda, sorry. You will likely have to use software/drivers supplied by PFC with the hardware. Sorry I'm not of much help I've never dealt with PFC hardware.

It's not a bug as such, its because you are overtaxing your system with autogen among other things, if you push the quantity too high along with other high settings you will start to see errors like this because FSX is giving priority to other parts of the simulation that are more critical to time sensitive data. Autogen scenery and clouds are a low priority and usually the first thing to show errors when resources are getting scarce.

The water shader setting in FSX may influence this quite a bit too so its best if you say what setting you are using i.e. "2.x low" for example. I also change the water textures from default with AS2012, so people are likely to see large variations in colour anyway depending on whether they are using default or not. The screen shot above looks ok to me though, I wouldn't call that excessive at all.

Did you reboot the PC, some bgl's remain in memory even after being disabled in the library, its another FSX bug.

I bet the green water is a UTX layering problem with FTXG, I don't use either product so I cant advise further, but my money is on FTXG having an exclusion at a higher level that is stopping the UTX water colour adjustments working properly.

Symbolic links How to. http://www.howtogeek.com/howto/16226/complete-guide-to-symbolic-links-symlinks-on-windows-or-linux/

Here are some mirrors for the Linda files mentioned in the first post in the thread. Occasionally the LINDA website is unavailable so these links can be used as a backup. They are located in my own private Dropbox. Linda V1.1 zip 5Mb - full package with all addon aircraft modules. LINDA-v1.11_without_modules.zip (zip, 5Mb) - complete LINDA without any addon modules (but of course standard FSX aircraft). LINDA Manual (PDF) -- read here on the installation process. Brian's beginner Guide: "Indroducing LINDA" -- New users should really read this first before using LINDA, it has all the information you are ever likely to need.

Its not working from here in the UK. Edit: then I tried it again literally 20 seconds later and it is working, lol. It seems that occasionally the LINDA website is unavailable so these links can be used as a backup. They are located in my own private Dropbox. Linda V1.1 zip 5Mb - full package with all addon aircraft modules. LINDA-v1.11_without_modules.zip (zip, 5Mb) - complete LINDA without any addon modules (but of course standard FSX aircraft). LINDA Manual (PDF) -- read here on the installation process. Brian's beginner Guide: "Indroducing LINDA" -- New users should really read this first before using LINDA, it has all the information you are ever likely to need.

Highlight the control in question then press ESC (escape).

You wouldn't be saying humbug if you wanted to create your own set of camera views that are in different locations to the ones that come with an aircraft. The manual way of doing it takes about 20 times longer than doing it with EZdok. Adding one camera on average took me about 6 minutes to place manually by editing views in a text editor. The same thing takes seconds in EZdok and requires no knowledge of the FSX view coordinates system.

They have a whole forum section of their own at two or more different forums that I know of, they get plenty of free advertising. I have no issue with customers extolling the virtues of a product in a none relevant thread, I have no problem with a competing developer setting the record straight when misinformation is being spread about their wares, but it is in bad taste when the developer starts directly advertising in a thread that is clearly a conflict of interest. That is all I have to say and I'll leave the thread now.

Julian I take it you missed post 19, 21 and 22 then, as that is what I am referring to as advertisements.

Advertising by commercial members is not allowed in a competing thread, what was said by the commercial member is advertising of improvements, there is simply no disputing that. This isn't something new either, this rule has been about for years and many commercial members have fallen foul of it over the years as I'm sure they will attest. I think what Stephen was referring to by fanboi'ism is the fact that users tend to swarm on a thread defending a product or berating another when they see the developer of said product enter a thread, Stephen was simply stating that that kind of behaviour is not tolerated at AVSIM, he was stopping it BEFORE it escalated to that point.

When a commercial member comes into a competing thread and starts promoting their product it's against the rules, it's as simple as that badfinger.

I'm sorry Dirk but you are misinformed if you are saying that frame rates are worse when using EZDok cameras instead of OPUS, EZDok has ZERO effect on the frame rate, it is not measurable. Have a look at the CPU time for yourself (CPU time is not enabled by default in task manager) and you will see this to be true. If you are seeing a drop then its unique to your system and probably some other software or AV engine is interfering. The general consensus over the years that EZDok has been available is that it has no effect at all on frame rate.

No that is untrue, there is zero measurable hit on the frame rate, it's no different than the hit you would get from moving the camera with the default move keys or by pressing the space bar and moving your view with the mouse.