Ian P
-
Posts
5,629 -
Joined
-
Last visited
-
Days Won
7
Content Type
Profiles
Forums
Events
Gallery
Downloads
Posts posted by Ian P
-
-
Hi Bob,
I'll message management and ask them whether anything has changed, but I've just tried two different service providers (3 mobile and Virgin Media) here in the UK and both have been able to connect without any issues.
It does sound like a DNS update issue still, but it is weird that two different DNS services can't find it at the same time. Far from impossible, but a bit odd!
Cheers,
Ian P.
-
I just managed to download OK from the "Updated Modules" thread - I suspect it was just a transient problem while a DNS table was updated somewhere.
Cheers,
Ian P.
-
Moved from FAQ to support forum. It's not a FAQ!
Ian P.
-
Moved out of FAQ to support forum. It's not a FAQ!
Ian P. -
It would be better to send Kev a private message with your e-mail address, bazvink.
If you hover your mouse over his username at the top left of his post (the "707fan" in blue), there's an option there to "PM this member". It would be better to send it like that, privately, than post it on an open public forum.
Cheers,
Ian P.
Forum Admin. -
It's worth remembering that English is not Volker's first language - although his English is a very great amount better than my German!!! :oops:
Volker was helping, but by the look of what I've seen, there's a bit of a language barrier here; people aren't understanding exactly what's being said by the other side of the discussion.
Anyway. Glad it's working.
Cheers,
Ian P.
-
Hi Terry,
I've had another e-mail from Volker, which explains another option, which also makes sense... You've shared your FS directory, evidently with permissions of "Everyone", which will work fine, although it'll make PC security types sob into their keyboards. The question is, is FSX also on your "W:/" drive, or do you use that only for scenery?
As Volker just pointed out to me, if the drive isn't shared and thus cannot be seen by the client PC, then FSC can't scan the BGL file to get the airport information.
Anyway. It's only partially the position in your scenery library that determines what overwrites what. It's actually a series of entries in the BGL file, which are usually added by ADE, so I suspect they will be there, which are what disables scenery at a lower priority in the library... Or they should. The problem is, that doesn't always seem to work 100%, which is really annoying!
The critical place to look is your Scenery Library inside the sim (i.e. through Settings/Scenery Library from the front page, or World/Scenery Library when flying). The theory is that Higher Priority (i.e. lower number on the right hand side, closer to the top of the list,) should take priority over Lower priority (higher number, further down the list) - provided that the two airport files use the same ICAO code and file structure.
MTX should usually be located immediately above "Propellor Objects". I'm looking at my development FSX-SE install here, so that would put MTX at Priority 19 on this install. Addon Scenery is at Priority 12, so anything in my Addon Scenery would overwrite anything that Burkhard has put in MTX, provided the "remove" code is present and the file structure is the same. As you say, the only reason I recommended editing Burkhard's rather than the default, to add the ILS is because he adds extra parking spots which you would otherwise lose and you may not see traffic as a result.
I thought one of Volker's recommendations was to only have one LEBB file present? It's always a good idea to disable one if you are using an alternative: Using Windows Explorer (not Internet Explorer!) go to w:\FSX\MYTRAFFIC\scenery\ and click twice on BR2_LEBB.BGL add ".passive" on the end to make it "BR2_LEBB_BGL.passive" and it will stop being read by the sim, thus avoiding all the problems.
Cheers,
Ian P.
-
It gives you an ability to briefly rapidly climb or descend, for example to avoid a conflict with another aircraft. In the real aircraft, the systems will stop you from reaching the stall, but that's apparently quite difficult to achieve in FSX coding, as every Airbus I've met yet has stalled or overspeeded when using Expedite.
Cheers,
Ian P.
-
The problem isn't that you edited the wrong file, Terry - the problem is that FSX is reading two BGL files for the same airport, which is a known major issue. At least yours isn't crashing, which a lot of peoples' sims do! What's happening now is that it's reading the ILS in the first file it sees (scenery.cfg can be ordered in a different order than your scenery library in the sim, which I suspect is what's happening here), so it's displaying it.
You really do need to ensure that one of the two is disabled, as both Volker and I have suggested, to ensure no problems between the two in the future.
Edited to add: Something that Volker has pointed out in an e-mail to me has just made me have another thought as well... There are permissions issues in Windows 10 when communicating with Windows 7, especially if you use administrative shares (c$, d$, etc.) - are you using the same username on both PCs and are they both able to read/write to folders on each other?
Cheers,
Ian P.
-
Right. We'll start with a simple question from me.
Have you added an approach as well, or just the ILS? If you do not assign an approach as well as the ILS, then the ILS will not work properly (it'll be visible to the user aircraft, but only the user aircraft) - this is a known limitation of FSX and ADE will build you a simple approach if you ask it to, but you do need to ask it to.
I would also VERY strongly recommend that you go into your w:\FSX\MYTRAFFIC\scenery\ folder and change BR2_LEBB.BGL to .passive or .bgl.passive. This is always recommended when you have multiple BGL files pertaining to an airport, because depending on what order FSX reads them in, either the MTX or your file can be read and that can cause many problems. Personally, I would recommend looking at Burkhard's BR2_LEBB file, rather than the default, to modify, as he will have added parking spots designed to work with MTX traffic that you will lose if you do not use his file. I strongly suspect, in this case, that while you are in fact seeing parts of both BGL files, because they are so similar, you aren't noticing, while FSC is only picking up Burkhard's modifications, not yours.
Additionally, as a UK CAA IMC rated pilot, with a lot of friends and aquaintances in the flight training and airline industries, I can tell you for a fact that "real pilots" only use an ILS for convenience, if their workload is high, or because the weather demands it. Pilots want to fly, not watch instruments while the computer flies so they will always prefer a visual approach to keep their skills up or to manually fly the ILS if the weather demands.
I have not seen the text of your e-mails, but the tone of your post here suggests that they are far from polite, which is wholly unacceptable when people are trying to help you.
I have a similar situation to you - a Win7 notebook as a client and a Win10 desktop as a server. Please send me your modified ADE file and BGL file to ian@the_site_this_forum_belongs_to and I'll take a look.
Ian P.
-
Comodo is a Firewall package, Pete.
What a lot of security software does now, rather than just blacklisting software that it doesn't recognise, is runs it in a "sandbox", where you can execute the application (e.g. an installer) to, basically, a virtual machine - it "extracts" it to a temporary store, rather than allowing it to write to the live Windows file system, Registry, etc. During this process it scans for "undesirable activity" and if it doesn't find any, it usually offers the user a choice to run the application 'properly'.Norton and Symantec both do it, as well, now. Like with all the hysterical, sorry, "heuristic", detections, I've never heard of one actually catching a piece of zero-day malware, but no-one has come up with a better method yet! To be honest, sandboxing is lot better than just blacklisting.
Ian P.
-
VORs in the real world have a fixed "guaranteed" range but you are right that they do not instantly vanish at that point. They will actually work a long way beyond that rang, but the critical thing is that you are not certain to receive it.
Obviously as with anything to do with atmospheric conditions, nothing can be truly guaranteed, but it takes a lot to knock out a VOR signal within the "guaranteed" range.
Ian P.
-
FSUIPC4 licenses are valid for all FSUIPC 4.xxxx versions.
Cheers,
Ian P.
-
Because the gauges in the Aerosoft Airbus products are manually coded and do not use FS functions, you'll almost certainly need to use LUA to read and write local variables in order to do that.
Ian P.
-
The "Local" in LVars refers to the fact that they are unique to that add-on, rather than "global", referring to the entire sim.
As an aside, you might like to check out LINDA (http://www.fs-linda.com/) which may already include the LVars for the Airbus packages. Unfortunately I don't use it (LINDA, that is - I do use the 'Buses) so I cannot say for sure.
Cheers,
Ian P.
-
There are examples of how to read and write Local Variables (LVars) in the documentation, which can be found within the "Modules" directory of your FSX installation.
Cheers,
Ian P.
-
Hi. Have you checked that there isn't a dialogue box asking for permission to do something (e.g. to run the FSUIPC module), hidden behind the FSX:SE splash screen and/or the Steam window? Press alt-tab to cycle through open windows to make sure.
If it isn't that, then I'm afraid Pete is away at the moment, but if you can post the contents of your FSUIPC log file, someone else may be able to help.
Cheers,
Ian P.
-
Hi.
Sorry for the delay in approving your post. Unfortunately Pete is away at present and I was travelling (or, well, stuck in a traffic jam!) for most of yesterday.Unfortunately, I'm not a cockpit builder (nor a LUA programmer) myself, just the forum admin, so I'll leave those with more knowledge and experience to answer your question.
Ian P.
-
The fact that you have changed e-mail addresses doesn't matter. If you purchased a license for FSUIPC4 then it will remain valid and will work with your original details on both FSX DVD and FSX SE (and Prepar3D...)
Please make sure that you are entering your details exactly as per the original order - copy and paste from your simMarket order details if possible - and it will work.Ian P.
-
Ah! That's a new one for me, thanks for letting us know.
When starting FSX, it usually sets Windows desktop back to "basic" mode, which disables Aero. I'm not sure why yours wouldn't be doing that, but as FSX has never been overly happy running alongside Aero desktops, that would make sense.
Glad it's working!
Cheers,
Ian P.
(Who's still a grumpy Smartie, sorry. ;)) -
Last time I looked in a mirror, it was a grumpy face, but neither yellow, nor with unattached hands and legs... Right amount of hair, though!
Anyway. Hmm. Those are the only two things I've ever heard of that have caused similar problems, personally, so I guess we're down to generic FS faultfinding time. When I got distorted text in my FSX installation, it was because of a change I had made in my nVidia driver settings.
Track down the fsx.cfg file (usually in C:\Users\[username]\AppData\Roaming\Microsoft\FSX) and rename it to fsx.bak or fsx.old, fsx.dis. When you run FSX, it will create a new one. Don't make any changes (FSX will look awful. ;) ) but check whether that fixes the problem. If it doesn't, which I suspect it won't, then you can delete your new fsx.cfg and rename your old one back to fsx.cfg to get all your settings back. If it does fix the problem, which is unlikely, then you need to reapply all your settings to the new file... Sorry!How much in terms of add-ons and tweaking have you done? Would it be a major problem to repair the installation through Steam? If not, then go to your Steam library page, right click FSX-SE in the listing, then "properties", "local files", "verify integrity of game cache..." - that will restore the original files and overwrite any possibly faulty ones.
Hope one of those helps!
Cheers,
Ian P.
-
Shufted up a level to general FSUIPC support.
Ian P.
-
If an axis or button on a controller is assigned both through FSX and FSUIPC settings, then you'll get conflicts and problems. You can either remove all assignments, or disable the controller. Personally, I remove all assignments from FSX except those I want to use (I always have problems with hat switches through FSUIPC for some reason, so leave them assigned through FSX...)
Ian P.
-
Are you running DX10 preview mode? If so, try turning it off.
I've also heard of certain graphics card driver settings doing that - are you altering the graphics settings through your card driver? If so, try resetting to default.
Cheers,
Ian P.
Thanks for the update
in (Former) FS Commander Support Forum
Posted
First posts from a new user have to be authorised by a moderator prior - unless you'd like a forum full of ads, spam and "dodgy content"... It does explain that when you press post. :)
I just got here, so your posts are now visible. ;)
Cheers,
Ian P.
Forum Administrator