Andydigital

Here is an example of annotator in action. Picture taken from this publicly available page here. http://msdn.microsoft.com/en-us/library/cc526979.aspx#CreatingBuildingFootprints

You don't seem to know the whole story, that is why I mentioned the annotator and unique 3D objects in my last post. Even Microsoft had to annotate the original textures by hand defining the autogen types onto the textures. A human had to define each texture sheet with autogen (with annotator), basically you draw polygons or lines onto the texture sheet, then assign a type of auto generated object to that line/polygon (shape). The auto part literally means that FSX procedurally places a type of building, tree or other object randomly to that position on the texture sheet, depending on what definition it was supplied with by that human. It was always defined manually by a human being. I know my stuff when it comes to scenery as I had been closely involved with scenery development (as a tester) especially photo scenery for quite a few years. I've also defined many square miles of autogen on photo scenery with annotator over the years too.

Indeed Gerry that is the reason, there is no point having autogen on top of photo scenery if it is placed randomly, seeing buildings and trees in the middle of roads and in water completely ruins the effect, default autogen exclusion is by design. But yes of course you can put autogen on top of photo scenery if you wish, many many developers already do this, one only has to look at a company like Earth Simulations to see this. The picture below taken from their website shows autogen hand placed (with the Annotator included in the FSX SDK) on top of photo scenery and most of it is hand placed autogen and not just unique 3D objects.

Are you sure you haven't just forgotten to remove the same assignment in FSX itself, you sound like you may have the parking brake assigned in FSX and in FSUIPC itself. So when you turn the parking brake on with FSUIPC FSX then sends the command too and that lets the brake off again.

Same for me push back with GSX works fine. Just remember to start number 2 before push if you want to be able to start number one before the push is completed. There is a bug that prevents engine starting when the GSX tug is connected to the aircraft, MJC and FSDT are trying to fix the issue. If number 2 is started before the tug attaches then you are able to start number 1 even while the push is in progress. Once the tug is disconnected you can then start as normal.

@@SierraHotel NONE of your other aircraft use an external simulation engine that just uses FSX purely for the visuals and world simulation. 1.006 does not bounce at all for me now and I use a huge amount of third party airports, meshes and scenery, etc. It's also butter smooth in the VC and Outside. My FSX.cfg is practically clean though, I dont mess about with Affinity masks or anything like that, about the only tweak I have is HIGHMEMFIX and a slightly higher than FS maximum for LOD_Radius, nor do I use DX10 preview.

Quite frankly the LD767 looked dated when it was released for the FSX, never mind now, definitely FS9 and earlier quality VC graphics, systems were good back then. The last time it was on my PC's was probably 4 years ago and its probably 5 years ago since I last flew it.

You haven't got the software in the correct mode then, I've just tested it and if you put the TrackIR 5.1 software in Track Clip Pro mode it actually turns the IR emitters off altogether, with a brightness setting of 0. I didn't realise it did this automatically, but for the reasons I stated earlier (about background noise from reflected radiation) it makes sense to turn it off in TCP mode.

You don't understand, the TCP is supposed to show light when you take a picture of it with an unfiltered camera, but it's not bright enough to see with the naked eye. You can try the same thing with a TV remote and a video camera, you can't see it with your eye but you will see it on the recording, if the lens isn't IR filtered. The IR emitters in the TIR base are many hundreds times brighter than the ones in the TCP (that's why you can see them with the naked eye) because they have to be bright enough to bounce the light off the reflectors on the Hat Clip. I'm 99% certain you can turn off the ones in the Camera sat on your monitor when you are using the TCP.

I'm pretty sure you dont need the IR emitters switched on the camera when using TrackIR with the TCP, the 4 emitters on the Camera are for bouncing the light off of the reflectors on the Hat Clip and shouldn't be need when using the TCP as it has emitters of its own. If anything you will be making the situation worse especially if there is a wall close behind you, as the IR will bounce off the wall creating more background noise.

I'm not sure why you think smaller light points make it anymore accurate though, it certainly isn't dim on my camera either. If anything I think the range of movement with the TCP is more restricted. You can very quickly get into a situation where two of the dots overlap one another when looking down and to one side. As soon as one of the dots disappears behind another the tracking stops dead in its tracks (pun intended). Getting in the same situation with the Hat Clip takes quite a bit of contortionism, a position you are unlikely to get yourself in unless you are looking at the very extremes of head movement, which you will never get near if your profile is tuned properly.. Still it doesn't matter really, at least we have more than one option and whichever one you prefer is the right option for you.

I notice not one iota of difference between the two, apart from the irritating wire rubbing my neck and it trying to strangle me if I move. The main reason for the TCP is for people who live in a location where they get a lot of IR radiation in the room they are using the TIR in, its supposed to improve tracking in that enviroment. Saying that though I do live in a location that gets really strong sun shining in thorough the window and I still don't need the TCP, I just have to turn the filtering up a bit in the driver software and it works pretty much flawlessly for me, even with the normal reflectors on the sprung steel clip you put on a baseball cap or similar.

@@Ron Attwood FireFox with the add-ons Adblock+ and Element Hiding Helper. It lets you block individual bits of code in a web page, like that irritating floating box. You have to be careful with it though as you can stop the whole page loading if you are not careful, everything is undo-able though. http://adblockplus.org/en/elemhidehelper

I believe all the stores now have 1.006, yes download it again from the store you bought it from. There is no need to remove the previous install. If you have made any customisations, like adding new repaints or anything like than, you will lose them if you do not backup the old files to a safe location, put them in a folder on your desktop or somewhere like that, as the new installer will wipe everything out that is currently within the Majestic aircraft folder structure.

Its not even a question of one or the other for me, TrackIR is better with EZDok. I blocked/removed that annoying flying message "click here to return to the top of the page' about 10 seconds after I first saw it on this forum, stupid bloody idea.

The problem is Majestic are a very small development house, they have their hands full with far more important matters at this time. Better hardware support will be coming later I am sure. They have already said that they will hook up the radio interface so that external hardware can use the default commands and there will probably be more options in the Pro and Training editions too. Its not like it takes forever to rebuild the macros again either.

Please don't post any email address without obfuscating it first, otherwise they will be inundated with spam from spambots which trawl forums looking for email addresses to send spam to. An example of obfuscation is support { AT } majesticsoftware DOT com.

My TCP broke taking it out of the box, lol. Fortunately I hate wires trailing across the room anyway and the Track Hat Clip fitted onto a nice golf visor works perfectly fine for me even in a very bright sun lit living room. I can wear the thing all day and I sometimes even forget I am wearing it, lol.

The default view system in FSX becomes very buggy when developers start using hotkeyselect in views that are not normally associated with a particular view key, i.e. the keys F9 F10 F11 F12. Its especially buggy if you have a different aircraft loaded in the same session that uses the F keys for a completely different type of view to that of the previous aircraft loaded. For example using Spot View instead of VC view with the F10 key, if I remember my F key view numbers correctly. I never use them anymore to be honest since EZCA came out.

I think you may have left out a pertinent piece of information, the fact that you are using a third party camera product like EZDok or OPUS. The reason the views are all now offset to the left like this is that in 1.006 the default VC view is now in the left Captains seat rather than in the right First Officers seat. When you create a set of cameras in EZDok and I presume in OPUS too although I do not own the later, the position of the EZDok camera is based off of and relative to the default VC view. So if the default view changes position so do EZDok's cameras. Simply edit the views and move them to the right and you will be back to normal. Edit: Ninja'd by another Andy.

I was actually talking to the thread starter not you FleetingThought, I could tell you didn't have a issue with waiting.

mgh was being sarcastic :LMAO:

Majestic.

You do realise don't you that at least a third of the world can be asleep at any given time of day. 3 hours is not long enough to wait believe me.

You need to email support and get your reinstall quota reset, you only get 5 install attempts per month. support { AT } majesticsoftware.com