Loz

Still no success I'm sorry to say. With all the settings that you have posted, FC2 will not even run, with a windows error "Flaming Cliffs 2 has stopped working" It is so frustrating that it works perfectly well on DCS Black Shark but not with any freedom of movement on FC2. :mad::mad:

Thanks for the clarification. I think I've already spotted what I might have done wrong, so I'll give it another try. Cheers

Well I've just tried that and it won't even run. By that do you mean you are only viewing it on one monitor or are you referring to some other setting. Thanks

Thanks Nate but excuse me for being a bit sceptical. I had seen his post and disregarded it because whatever he has done does not give the effect that we are after. Why for example, does his screen shot really show 3 individual screenshots joined up. That is certainly not eyefinity. I'm not sure what he has done and he isn't replying to any questions. After researching more of his posts I'm even more at a loss to explain his results. :(

Yes I've already researched that thread but none of it is tried in Eyefinity. Just single widescreen.

I see that no one has replied to your problem XysteR and I'm sorry to say that I don't have the answer as I have exactly the same problem. It's stopping me dead at the moment and since I've gone to a lot of expense to get the setup, it's a great disappointment. I'm gonna try portrait mode and see if that's workable with the A10 (my preferred bird)

Well thanks ZaltysZ but I hope that you are wrong and there is a fix because if there isn't then this isn't very good when so many more people are going for Multi Screens / Eyefinity especially with Flight Sims.

Thanks for your input but I don't think that can be right. If you look at the shot I've taken there wouldn't be any of the aircraft in view if I panned to the left. Thing is it will not let you do that! As soon as I shift my view, be it with the mouse, TrackIR 5, or the Num Pad, it tilts upwards and all you can see is sky. Yes, if I zoom in it will then progressively (the more zoomed in the further down I can tilt) let me look down. Finally I have Black Shark and have none of these problems??? I have tried matching View.lua to the BS one (they are nearly identical anyway) with no improvement. Anyone else, particularly if you have eyefinity running well, anymore ideas? :helpsmilie:

FC2 and Eyefinity????? I've lost it now. Spent 21/2 days waiting for a serial number and now spent the last 6 hours trying to fathom out why DCS Black Shark works perfectly well with my eyefinity setup and FC2 doesn't. No matter what I try with the \Config\View\SnapView.lua files, when I zoom out to be able to see wide screen the "panning plane" tilts such that at max zoom out you can only see sky. If you reduce the zoom in you can then tilt down, but it's so bad that to see the lower consoles you have to be almost fully zoomed in. I've used the search facility and although someone else reported the same there was no reply to help him. I have tried many changes to both the SnapView and View lua's but to no avail. This is how it looks at a not unreasonable zoom out, but I am unable to pan down at all. It's driving me nuts Please Help. :helpsmilie:

Yep Just checked and got mine too. Thank you for your help EtherealN

I have just received this email Greetings, Last weekend English Flaming Cliffs 2 serial numbers were not issued after purchase. In a day a serial number will be added to your account. It'll be colored in orange and listed on the page with your order details. See http://lockon.co.uk -> Login -> My purchases Please accept our sincere apologies for this issue.We are working hard on it. -- Regards, LockOn.ru administrator Polina Byvalova Still not very happy. Why should it take a day to sort out and if they can take the time to post the mail to me then why not include the Serial Number?? All rhetorical questions (don't require an answer) Just venting my frustration as I am one of those sitting here quote "having purchased the software in good faith, patiently hitting the refresh button on their browser" I've just learnt something from all this that I didn't know before, so there, that's some good come out of it. Refresh is "CTRL + R"

Caz5311 What a resoned and well thought out response to this problem. Bravo I wish that I could have composed such a mail but in lieu, how about this, GIVE ME MY B.....Y SERIAL NUMBER NOW. (No smilies)

Guess so For RAD2112 we are not alone mate. A whole bunch have posted here with the same problem.

Add me too. Just wish I'd seen this thread before taking the plunge and looking forward to getting this going today.:joystick: Still would have bought it but wouldn't have expected it till (I hope) tommorrow. Dislocation of expectation and all that. BlaaaaaaaaaaaaaH

I have exactly the same problem. Does the automated issuing of serial numbers (can't believe it's done manually) take the weekend off???? This is annoying.

I'd love to try this as I have the hardware, (see sig) but just put off trying to sort out the config in the .lua. Read people having trouble getting setup. Can you give me more of an idea of the setup required. Thanks :thumbup: Both really good videos by the way.

I think you'll find that the setup is Eyefinity but the A10 video is FC1 not 2

Mine certainly does. :megalol:

A marvelous piece of kit guys. Thanks very much to DickDastardly and Gadroc. My only problem is I can get everything to work except the display part of the navigation control panel!! The nav panel buttons all work if I check inside at the primary display, and everything else works within the TouchPanel screen Anybody else had this prob??

Many thanks to both of you (Lange and Leolasindar) for taking the time to help me out here. I think I'm there now and put a lot of it down to not having worked with Cougar files for sometime now. I'm just going to have to move the trim button down to 4 Down as that is where it used to be on the Wessex HC Mk2 (similar to the S 58 ) that I flew for some years in the RAF (mind you that was some time ago LOL) Out of interest, that was flown with ASE (Auto Stabilisation) engaged in normal ops and the process of trimming was exactly as described for the KA 50 ie. Trim / move Cyclic / Release Trim The spring feel was incredibly stiff and didn't allow for smooth control. We did practise flying it without the ASE engaged (ready for any realtime failures, which in my 7 years and 2500 hours never happened.) When doing this we released the Trim totally and flew with a really loose (Hydraulicly overpowered) "feel free" stick, somewhat like the old Whirlwind (Sikorsky S55) A tricky busines, because if you let the cyclic go for any reason, it would fall into the nearest corner and the rotor disc would follow with potentially fatal results. Happy days. Thanks again

Does anyone know what "Joy_?" is used for the Cougar Microstick. Just want to keep things simple at the moment, without programming the Stick. Yea I know, not making the best use of the Cougar, but for the life of me I can't correlate what loaded with Legolasindar's profile and what was shown on the JPEG. Most didn't seem to use the commands as shown. ?? :helpsmilie: Just remembered another problem that occured with Foxy when trying to amend the .tmj with the Trim additions from Rohnt in the "Cougar owners must read" thread. Firstly the layout as read by Foxy was all wrong, with no spaces between I/ O/, and the command, but even when I sorted that all out, all I got was a Compiler Error in Foxy, which I've never seen before?? Any help Much appreciated.

Thanks for the help above. Slayer - it was strange that the DCS.exe was showing in the Nvidia Control panel, so I assumed it would apply the default SLI settings but as you said, nothing was showing (SLI sidebar indications) till I actually assigned a profile. But I have to agree with Baka, that the framerate is far higher without SLI selected!! Yet another case of a Sim / game implemented without SLI support. My other problem re the Joystick not working was solved by a new installation and I shall be far more careful with changing .lua files in future.

Further to this I've found that the Joystick problem above is only happening in Simulation and not Game mode. By default, in game mode, my Saitek Cyborg is recognised and works as expected. So what have I done wrong, in Sim mode for it not to work??

First of all great sim, really looking forward to getting to grips with it. My Nvidia Control panel (180.48 drivers) is set to SLI with the side indicators ON. The game is set as default to Nvidia SLI, but in game the indicators are not showing at all. Making me think that this is not working with SLI...?? Secondly, I can't get my simple Saitek Cyborg Joystick to work in game, ever since I tried to change the Axis control sliders. (it did work previously) It now is showing as OK in windows control panel, the two buttons I changed using the Saitek editor to T and LAlt T (for Trim and Auto Hover) work in game but no control movement. Any help much appreciated guys. Thanks :doh: :doh: