LittlePaulio

Hi, I had posted earlier about getting sick of Orbx and figuring out which options I really need. I had considered switching scenery products, but I just don't have have the spare cash to invest in UTX/GEX. So today, after starting with a pretty base FSX installation I ran Orbx Global Vector 100 first. Went fine. I then installed FTX Ireland and it's patch- again no problem. I also own FTX England and Scotland. As I am still very much learning the solid basics, and I like low-level flying, I fly GA aircraft exclusively and Ireland certainly looked amazing with Global base or the Land Classes. It's never stated outright (I don't think), but maybe Global Base is for a complete world overhaul and it's not necessary to run the other products (please correct me if I'm wrong). I know I lose the option of hybrid mode (I assume) and the rest of the world will be default FSX textures. Can anyone confirm if I'm correct please? Scenery loading times have been cut in half imo. Any feedback on this, or if the European LCs would add anything to a dedicated FTX region would be much appreciated. Thanks,

I think these are laptop type keys (or chiclet style as VeryBumpy described them). The Corsair we were referring to are mechanical keyboards, and can be quite 'clickty-clackty' in comparison. I actually think that keyboard is a beautiful looking thing, but I presume they are printed on and you're stuck with their configuration? (Which is no bad thing if that's what you use) I take it you don't use FSUIPC PWJ? Cheers

I thought the corsair cherry reds were the noisiest of them and the brown the quietest. Could be wrong though.

Hey, I just change the zoom levels depending on the plane I'm flying, I find I need to usually zoom out before I'm happy. It's down to the user really, just experiment and see what works best for you. This is in FSX, just to confirm.Cheers

Thanks very much guys! really appreciate it!

I got into FSX boxed just as Orbx was redesigning the FSX scenery as a series of modules. I have recently realised that I probably just got swept along in the hype and it seemed to be the most sensible solution to upgrade the default scenery. Of late I've really being regretting my impulsiveness. I mainly fly in and around Ireland and England and I fins that with all Orbx products turned off and all the FSX sliders pushed to the right, outside of the cities (I have London Heathrow and Dublin by Aerosoft) I just don't notice that much of a difference. I think REX HD 4 helps a lot as well. I have suffered two FSX drives crashes recently and trying to track down all of the Orbx bits and pieces has led to a lot of duplicate files and confusion over products I never bought in FXT 2 central after reinstallion that has led me to find a simpler, less expensive solution Just wondering if anyone is in the same place as me and could recommend some free or cheaper mesh and vecture solutions for Western Europe. There are plenty of options for the major airports thanks to Aerosoft among others. Just interested in peoples opinion in possibly the one sub-forum who would most likely challenge my opinions. Interested in any feedback. Thank you

Yeah, that's right GB, that's whats happened. It was a hilarious comment in retrospect

I bought the Corsair K65 RGB, and while it's still mounted on my yoke, I rarely use it, never mind pay any attention to the colours I had mapped out. I have since deleted the default key assignments and just use it for running a couple of LUA scripts. I find those cherry red keys to loud anyway. In fact, you have made me realise that I could sell it, buy a another small form factor but, cheap, cheap keyboard, and hopefully not have the one Warthog Dual Throttle I have found new sell out too soon. Thanks guys!

Lol, ok, I'll bite. My initial problem was that my PC wouldn't boot when the pedals were plugged in. This was worrying enough, but when I downloaded the software it continually crashed for no apparent reason, here, let me quote Milan on this; On the failure of my Pc to boot he was very comprehensive in his conviction that it was how some Intel MBs (X87s, X97s, X99s) handled xHCI handover which is initially handled by USB 3.0 xHCI. He gave me a slew of articles which documented how users of high polling and high precision devices,think devices like the TM HOTAS Warthog or gaming mice with whatever stupidly high dpi were causing unforeseen problems for certain chipsets. But don't let me hoard those articles- enjoy: I didn't pretend to understand the technical side of things, I just new I had a very customisable BIOS. So, I went through the settings and found the USB 3.0 xHCI one as well as the handoff one, which Milan wasn't aware of this setting. he hadn't come across any other user try his method. So while got overexcited and left the USB 3.0 xHCI disabled I had found a fix for motherboards which have this problem and some interesting new information for future firmware updates for the affected chipsets. Because, as I mentioned in an earlier post, my XBOX controller didn't work properly with the pedals plugged in, and as luck would have it I decided was finished with FIFA for good, I uninstalled the two devices (receiver and controller), Milan reckons that having them both installed in my system (which is the bottom of the range of the Asus 97Ks, that was probably affecting my pedal calibration results. I had still be using them with FSUIPC, but I knew the pedals weren't calibrate properly for my x and y axis defaulted angle, which I had increased. And this continued to bug me, til it all worked out. You've been a real lateral thinker with your continued, increasingly annoyed statements that calibration was simple. It must be great thinking that if something works straight away for you and the majority of users, that the minority are all guilty of 'user error'. What's gotcha so worked up ''Gboz? God knows that name suits you now. Cheers Ron, at least for you it wasn't something I had said or how many posts I was making. And, Mark, who knows his way around a Pc to put it mildly was also having problems although different ones seemingly. Questions Gboz?

Not that anyone is particularly bothered any more, I finally got my Crosswinds properly calibrated with the MFG software- and it makes a difference to have them calibrated properly. Everything is just that much more natural feeling and accurate. All it took was me continually harassing Milan until he very graciously agreed to come on Team Viewer and go to the process. Which was exactly what I thought I had done on numerous occasions. Anyway I was too happy to be embarrassed. He is such a nice, genuine guy who knows what seems simple to him (and lots of others around here!) isn't for everyone. I'm just hoping it was the un-installation of my 360 wireless controller and drivers that had something to do with it! Anyone new with problems feel free to ask, you probably won't though as Milan is working on new software that will cover the older electronics of the first models and our newer one. Plus iron out a bug or two. Cheers

Hey GBoz. I have still been unable to calibrate using the MFG software (only have 50% of raw data output afterwards everytime), so I've gone with the default settings and then calibrated in FSUIPC. It only occurred to me in the last few days that I'm calibrating on top of an MFG default calibration. FSUIPC can only see the calibrated MFG so by calibrating further I must be seriously reducing the range of output of the pedals. I read in the 1.4 manual that you can turn hardware (MFG) calibration off, but with version 2 I can't be sure what box I need to untick: This is from the laptop, hence 'no device found'. Or should I leave all calibration fields at '0'. Anyway, hoping to get on TeamViewer with Milan at some stage. Thanks. Hi Blaze, I just asked Gboz a similar question related to this. If you are calibrating in FSUIPC after MFG, how can you be sure exactly how it's calibrated, as they use separate calibration mechanics- one responding to the users physical input and pedal setup and the other based on whatever the user chooses the values to be? Am I making any sense? Oh, and now would be a good time to point out that my advice to disable Intel USB 3 XHCI if your Pc refused to boot with the pedals plugged in was made without even pausing for a second to consider the ramifications of that was just plain stupid. Which I'm sure was obvious to those who read it. You simply need to disable EHCI handoff in the bios (which prevents WIndows from taking control of the USB hub too early for fast polling devices like the MFGs or certain gaming mice with ridiculously high DPI). Apologies on that. Schoolboy error.

What I did was in the MFG software was just hit 'apply' I think. This restores the pedals to the default values. I did this because after my calibration the pedals were no longer outputting the 100% of raw data in that other application (also in the MFG folder). That did the trick as far as the pedals registering 100% movement on every axis. I then assigned and calibrated in FSUIPC (as opposed to just assigning). This might not be the recommended method, but it's worked a treat for me. I have also changed the angle of the pedals to somewhere between 35 degrees and 40 (they didn't match up when I used the written values under the pedals, so I just lined them up by eye, which Milan says is fine. You should try calibration straight to FSUIPC and see what it registers when you move the various axes. It sounds like it's registering rudder movement and braking simultaneously. Either that or FSX is still registering input data from an old set of pedals or somewhere else. I think you calibrated in FSUIPC as well GB if I'm not mistaken? BTW GB, do you have a separate button for 'brakes', or do you just press both toe brakes at once?

Sorry to hear that Mark. However your problem sounds slightly different to mine. Just a couple of questions- Will your PC boot with the pedals plugged in? Can you successfully upgrade the firmware with the MFG Configurator (I know I was doing that completely wrong), and if you can does the MFG software crash repeatedly for you. I never even got as far as using them in FSX until my fix. Oh, what motherboard do you have, that could prove crucial. And while we're at it, where are you assigning the pedal's functions, in FSX or FSUIPC? I forgot to mention, the Xhci fix was in the BIOS alright. Should mention that my XBOX wireless controller won't function correctly until I unplug the pedals. Not a big deal though.

Got it working thanks. It was either setting them up in windowed mode or setting panel stretchering to 0 in fsx.cfg. Thanks for the input GB, it is good to know, as I am also having problems displaying lua output to my new monitor. But that's another problem for another day. Thank for the feedback GB,

Hey GB, Yep, it does. I have set panel stretching in fsx.cfg to 0, but have yet to test it. Any ideas?

Ok. Thanks for the prompt reply David.

Thanks Ron, Appreciate your reply, but my resolutions are set correctly in fsx.cfg. Still, with TrackIR5 and EZDok, I probably don't the 2d panels. I'll still have a tinker around though. Thanks as always for your feeback. I actually have a spare ACERG24 24" 1900x1200 that you're welcome to. It's a great monitor for a TN panel. I suspect the postage to England (I'm presuming you're English for some reason) would prove prohibitive, but I can check it out if you're interested.

Sorry to jump in here. I'm just wondering why you have disabled wide view. i have just purchased a 3440x1440 curved Samsung. Things have a fish eye look in VC, any idea what settings I should be using? Thanks,

Cheers Ron, I certainly will have total confidence in purchasing from Milan in the future. I'm going to be cheeky and ask you a question regarding monitors. It will only be relevant if you're using a 2 (or more) monitor setup where there is a great disparity between the respective resolutions of the main monitor and the second monitor. I have already posted in the relevant section, but I'm just hoping you might know. If you don't have a setup as described, no worries. Thanks for your reply,

Hi, I decided to post this separately in case the mention of FSUIPC meant people didn't view the post. This is a long-time problem I realise, I even had it when I had two 24'' monitors (1900x1080 & 1900x1200). I have since upgraded to the 34'' Samsung 3440x1440 curved display. I held on to the 1900x1080 monitor to place display 2D flight panels and instruments. However, now when I drag them across they unsurprisingly are still set up for the 3440x1440 display and are absolutely huge and pixellated. I always play in full screen with DX10 and the paid version of Steve's fixer. Is there a fix for this in the fsx.cfg file (it currently has the correct resolutions for both monitors). I use a GTX 980 btw with displayport for the main monitor and HDMI for the 24" monitor. Any suggestions? Thanks in advance

Hi everyone, I know this isn't exactly the appropriate thread for this problem, but I've already posted in Pete Dowson's forum and haven't received a reply yet. But I do have a more relevant problem as well that I will post separately. I recently upgraded my 24" 1900x1080 monitor to the Samsung 34" curved 3440x1440. Big, big change, but all good. My FSUIPC problem relates to a Lua script I used to output text values to my monitor. Since upgrading, when I press the relevant key, they're nowhere to be seeing. In the unlikely event that someone else has experienced a similar problem I would appreciate any ideas. Thanks,

I had been having terrible problems initially with these pedals (which I know sounds like sacrilege in this or many other threads!). First of my PC wouldn't boot with the pedals plugged in. I then found the MFG configurator crashing literally every single time I attempted to calibrate. Just reporting this to report what a responsive, helpful, patient and genuinely nice guy Milan is. He initially was confused by my problems but obviously did his research. Apparently it was to do with Intel USB 3.0 Xhci which apparently has trouble with devices with very high polling rates. So after trying every other solution I could think of (unplugging every other non-essential USB device) neither problem was solved. Getting kind of desperate I continued to email Milan, who offered to go on TeamViewer with me to help me out. I finally went into my Asus Z97K MB and found the entries for Intel USB 3 Xhci and the associated Echi handoff, disabled them, and, voila, my PC booted fine with everything plugged in. I just set the Configurator to default values and decided like GBoz (thanks again for your help!) to calibrate with FSUIPC. Now everything works like a dream! I will eventually try the official method of calibration, but I just find all the values there confusing. I'm just surprised why no-one else has experienced this problem, Intel Xhci is pretty ubiquitous with it's 1150 socket motherboards and probably their newer models as well. Anyway, alls well that ends well, and now I realise what everyone was talking about. It's such a pleasure not to have to reach across to my T1600M for rudder control. I have the standard Saitek yoke/throttle setup. Can't praise Milan enough and am seriously looking forward to the pedal variations (and whatever he may be working on) being developed in the MFG workshop! Cheers everyone,

Thanks Man, just got it calibrated. Some good advice too about rudder tension. I really appreciate it. Thanks,

Thanks GB, it's just so hit and miss now. I'v managed to update finally- ( I was doing it so wrong!) Now I don't know what a successful calibration is supposed to look like. I love Milan, he's such a nice guy, but for people like me really should have written some sort of manual for V2. I've watched all his YouTube videos and I still don't know what the 'virtual button' is for for, why my x axis always has it marked. Why my default ' Avrg filter? and Round filter' are completely different for my x and y axis. Too many filters. But I know I have to calibrate in this program otherwise it'll never be properly accurate. I did change the angle of the pedal but there's too many things gone wrong for that to explain it. Sorry, very tired and frustrated. It's good to know once I calibrate I'm good. Thanks for your response. Hopefully I can report back with success.!

After getting all my software reinstalled and the new TrackIR5 update back on speaking terms it was quite frustrating having problems with the the MFGs. I already realise that I was updating the software and trying to calibrate it completely wrong. However, a couple of questions I feel a bit stupid not knowing as everyone else obviously knows the answer- once the pedals are calibrated can you close the software and not have to assign anything in FSX or FSUIPC? You've been my go to guy Ron and I'm pretty sure you'll have some sort of answer for me. Also, do you think I should loosen my rudder tension a bit in order to prevent the brakes kicking in when not wanted? Not to take you for granted of course, but I just feel you know your stuff. I'll definitely owe you more than one. Thanks in advance,