Loz

Very definitely worth it, I would say. Unlike some others, I've had my Cougar since it was first released and had no problems at all, with it. Considering how long ago that was, then the value for money with that, was immense. Don't see that the Warthog will not be a similar if not better investment to my Flight Simming for another 10 or more years. Gotta get the MFDs too for the complete set. (Shame they aren't built to the same standards though) ps. Love the little mechanical widget to get rid of the Reheat Detent in the Throttle.

Even after bearing in mind all the "health warnings" (Alpha build, still WIP etc) I'd also like to know what sort of FPS Viper gets on Av, as my spec is very similar. Pretty please. :)

I would like to add my plea for a Colour, spiral bound manual with Tabs. I'll pay whatever it costs, not that "money is no object" but with the amount of work that has gone into this sim, I see it as being a good investment in my Sim Fun Time for a good few years.

How about this one. Seems to carry on from the one you found. It would appear that "It only take 2-3 weeks to upgrade from the A to the C model" quotes one of the pilots. LOL

No We are both using the HD5970, a single card with two GPUs and they are running in Crossfire.

I've got the same spec CPU as yours and I run 6024 x 1200 on three Dell 2410 monitors, using an ATI HD5970. (ie the equivalent of two 5840s) and in both FC2 and BS get frame rates averaging 50. That is not the problem, what is though is getting the "head" postion correct for the FOV. Hard to explain but certainly in FC and FC2 when you zoom back from the default view (which is far too close) and you pan your head around, it runs on an inclined plane such that you can not see down when you are looking out to the wings. Strange. I have succeeded with altering some of the view settings and have got it to work satisfactorily in the instant flight but you have to make the same changes to each mission view.lua to get them to work correctly. A real pain. I have posted on the subject before so use the search and you should find it.

Well I've done some more googling and found out that at least ED didn't invent these. Photo taken of A-10C 81-0960 from the 81st Fighter Squadron, 52nd Fighter Wing Spangdahlem AB, Germany, was taken by Warthog News contributor Mariusz Krawczyk during Radom Air Show 2009 at Sadków Radom Airport, Poland. This one of the staboard side shows that ED was far "neater" at tying the knot that the USAF. LOL :D

Can't say what the price would be in the USA but I've got an i7 920 (2.6 Ghz) overclocked to 4Ghz in a Cosmos S case (very big) cooled with a CoolerMaster H50. This is an integrated sealed liquid cooler with radiator and does a really good job. You've got to have a reasonably big case though to fit the radiator.

Could they be unofficial "mods" for holding maps, charts to stop them moving around the cockpit, or am I being too sensible here.

Insignificant they may be but they are puzzling me as to their use. That is the pieces of what seems to be cord that are shown attached to the lower side of the front canopy, viewed from inside. Anyone know what they are used for in the real world????? :pilotfly:

I've just encountered the same problem. Basicly, out of the blue, I coundn't start BS. It stated that I needed to insert a disc also. But I've always had the downloaded English version and yes I had installed the English patch some time ago. Anyway I just had a punt and reloaded the patch and all is OK again. Strange.

Further to this. I have been looking and testing only using the Quick Mission and discovered that this weird TrackIR behaviour is only on that flight. The other missions seem to be OK. Obviously, no problem, and I can live with that but still would like to find the cause.

Tried all that as I said in my first post. :cry:

Yes I've done the game update and the point is guys, that it's working fine in everything BUT the A10!! So surely that means it is something in the Flaming Cliffs 2 side that is set incorrectly.??

I had to reload my TrackIR software as for some reason it disappeared. After having done that I have a wierd result. In the A10, and only the A10, when I look everywhere but to the right, it's all OK. But if I look to the right the view goes to the left......!! I've checked the assignments in the Control / TrackIR menu and they are all OK. I've tried deleting the TrackIR.lua in the config/input/aircraft/a-10a/trackir folder for it to write another one, but still no success. Help!! :helpsmilie:

Yep ICDO, I've just disabled Bezel Management to confirm that it is the cause of the Radio comms menus not showing up. It's almost as if the positioning of the menu is done from the right of full screen rather than the left?? I agree, come on ED, fix this for us eyefinity users, please.

Yes that's exactly how mine apprears too. And I'd like an answer too, so more than happy to bump this thread.

Yes indeed ICDO, I should have included that too. The mouse needs to be pointed and clicked just below where you want it to take effect.

I've finally got my eyefinity setup 6024 x 1200 working in FC2 but a minor thing, I can't see the radio command dialogue box. Well not quite correct, I see the opaque box that the text usually lies in but no text. Is there any file that I can change to be able to see the text in the radio command box??

For Nate Thanks for that I shall have a look at those mission miz files.

For JimMack yes I didn't show that in the short video but here is a still looking fully down with TrackIR.

Ok Got a short video together here. Firstly it's not brilliant quality, but the file size would be so large otherwise. Seconly on watching, the clipping that takes place in the peripheral screens is far more evident than when in game. If you watch with your focus of attention being on the centre third of the screen you will get the proper impression. But what it does show is that I have achieved a full panning view of both inside and out. Which is what I was after. Now I have moved on to some of the missions I find that the centre of view is different again and hasn't carried over from the quick mission which is shown here. Does anybody know why that is? Do the missions use different view, sever or snapview lua's?? Edit: Further research and not all missions have the same "Head Point." Just found one, ie the practice bombing, that is the same as the "Quick Start"

OK guys. My setup is in my Sig below and in addition I am running Catalsyt 10.3a WHQL video drivers. Config\MonitorSetup\1Camers.lua = function(p) return p; end; name = _('1 Screen'); Description = 'One monitor configuration'; Viewports = { Center = { x = 0; y = 0; width = screen.width; height = screen.height; viewDx = 0; viewDy = 0.2; aspect = screen.aspect; } } Notice the viewDy = 0.2 BlackShark\data\Option.lua options = { ["difficulty"] = { ["padlock"] = false, ["easyRadar"] = false, ["miniHUD"] = false, ["birds"] = 0, ["optionsView"] = "optview_all", ["permitCrash"] = false, ["immortal"] = false, ["map"] = true, ["radio"] = false, ["labels"] = false, ["tips"] = true, ["aftSwitching"] = true, ["cockpitLanguage"] = "english", ["units"] = "imperial", ["easyFlight"] = false, ["altTrimmingMethod"] = false, ["externalViews"] = true, ["iconsTheme"] = "nato", ["fuel"] = false, ["weapons"] = false, ["setGlobal"] = true, ["geffect"] = "realistic", }, -- end of ["difficulty"] ["views"] = { ["cockpit"] = { ["mirrors"] = true, ["reflections"] = false, ["russianHud"] = false, ["avionics"] = 4, }, -- end of ["cockpit"] }, -- end of ["views"] ["sound"] = { ["world"] = -4, ["radioSpeech"] = true, ["cockpit"] = 0, ["volume"] = -4, ["headphones"] = -4, ["music"] = -4.5, ["subtitles"] = true, ["gui"] = -4, }, -- end of ["sound"] ["graphics"] = { ["multiMonitorSetup"] = "1camera", ["color"] = "32", ["heatBlr"] = 1, ["scenes"] = "high", ["water"] = 2, ["fullScreen"] = true, ["visibRange"] = "High", ["aspect"] = 5.023, ["textures"] = 2, ["shadows"] = 1, ["effects"] = 3, ["width"] = 6028, ["lights"] = 2, ["height"] = 1200, ["civTraffic"] = 1, ["resolution"] = "6028x1200", ["haze"] = 1, }, -- end of ["graphics"] } -- end of options Config\Server.lua -- View scripts -- Copyright © 2004, Eagle Dynamics. -- Don't change existing values, they are requested from Ñ++! -- Use these indices in Snap and CockpitLocalPoint tables. dofile("Scripts/Database/wsTypes.lua") PlaneIndex = { iSu_27 = 1, iSu_33 = 2, iSu_25 = 3, iSu_39 = 4, -- Su-39 or Su-25T iMiG_29 = 5, iMiG_29K = 6, iA_10 = 7, iF_15 = 8, iKA_50 = 9, } PlaneIndexByType = { [MiG_29] = PlaneIndex.iMiG_29, [su_27] = PlaneIndex.iSu_27, [su_33] = PlaneIndex.iSu_33, [F_15] = PlaneIndex.iF_15, [su_25] = PlaneIndex.iSu_25, [A_10] = PlaneIndex.iA_10, [MIG_29K] = PlaneIndex.iMiG_29K, [su_39] = PlaneIndex.iSu_39, [MiG_29G] = PlaneIndex.iMiG_29, [MiG_29C] = PlaneIndex.iMiG_29, [su_25T] = PlaneIndex.iSu_39, [KA_50] = PlaneIndex.iKA_50, } function validate(tbl,itype) return tbl[itype] or tbl[su_27] end DisableCombatViews = false -- F5 & Ctrl-F5 ExternalObjectsLockDistance = 10000.0 ShowTargetInfo = false CameraTerrainRestriction = true CockpitLocalPoint = {} CockpitLocalPoint[PlaneIndex.iSu_27] = {8.15, 1.38, 0.0} CockpitLocalPoint[PlaneIndex.iSu_33] = {8.35, 1.35, 0.0} CockpitLocalPoint[PlaneIndex.iSu_25] = {3.5 , 0.4 , 0.0} CockpitLocalPoint[PlaneIndex.iSu_39] = {3.406, 0.466, 0.0} CockpitLocalPoint[PlaneIndex.iMiG_29] = {4.92, 1.35, 0.0} CockpitLocalPoint[PlaneIndex.iMiG_29K] = {4.9, 1.254, 0.0} CockpitLocalPoint[PlaneIndex.iA_10] = {4.201, 1.55, 0.0} CockpitLocalPoint[PlaneIndex.iF_15] = {6.5, 1.238, 0.0} CockpitLocalPoint[PlaneIndex.iKA_50] = {3.188, 0.39, 0.0} EyePoint = {} EyePoint[PlaneIndex.iSu_27] = {0,0,0} EyePoint[PlaneIndex.iSu_33] = {0,0,0} EyePoint[PlaneIndex.iSu_25] = {0,0,0} EyePoint[PlaneIndex.iSu_39] = {0,0,0} EyePoint[PlaneIndex.iMiG_29] = {0,0,0} EyePoint[PlaneIndex.iMiG_29K] = {0,0,0} EyePoint[PlaneIndex.iA_10] = {0,0,0} EyePoint[PlaneIndex.iF_15] = {0,0,0} EyePoint[PlaneIndex.iKA_50] = {0.09, 0, 0} --local old_aircrafts_6DOF = {x = {-2,2},y = {-2,2},z = {-2,2},roll = 90.0} -- {x = {0,0},y = {0,0},z = {0,0},roll = 0} --local old_aircrafts_6DOF = {x = {-0.02,0.05},y = {-0.03,0.03},z = {-0.03,0.03},roll = 90.0} --original FC2 limited 6DOF local old_aircrafts_6DOF = {x = {-0.02,0.35},y = {-0.35,0.18},z = {-0.35,0.35},roll = 90.0} limits_6DOF = {} limits_6DOF[PlaneIndex.iSu_27] = old_aircrafts_6DOF limits_6DOF[PlaneIndex.iSu_33] = old_aircrafts_6DOF limits_6DOF[PlaneIndex.iSu_25] = old_aircrafts_6DOF limits_6DOF[PlaneIndex.iSu_39] = old_aircrafts_6DOF limits_6DOF[PlaneIndex.iMiG_29] = old_aircrafts_6DOF limits_6DOF[PlaneIndex.iMiG_29K] = old_aircrafts_6DOF limits_6DOF[PlaneIndex.iA_10] = old_aircrafts_6DOF limits_6DOF[PlaneIndex.iF_15] = old_aircrafts_6DOF limits_6DOF[PlaneIndex.iKA_50] = {x = {-0.02,0.35},y = {-0.15,0.21},z = {-0.26,0.26},roll = 90.0} function GetCockpitLocalPoint(iType) local p = CockpitLocalPoint[iType] return p[1], p[2], p[3] end function GetEyePoint(iType) local p = EyePoint[iType] return p[1], p[2], p[3] end function Get_6DOF_limits(iType) local p = limits_6DOF[iType] return p.x[1], p.x[2], p.y[1], p.y[2], p.z[1], p.z[2], p.roll end function SetCockpitLocalPoint(iType, x, y, z) local p = CockpitLocalPoint[iType] p[1] = x p[2] = y p[3] = z end -- Camera angle limits {horizontal angle max, vertical angle min, vertical angle max} CameraAngleLimits = {} CameraAngleLimits[PlaneIndex.iSu_27] = {140.0, -75.0, 90.0} CameraAngleLimits[PlaneIndex.iSu_33] = {140.0, -75.0, 90.0} CameraAngleLimits[PlaneIndex.iSu_25] = {95.0, -65.0, 90.0} CameraAngleLimits[PlaneIndex.iSu_39] = {110.0, -80.0, 90.0} CameraAngleLimits[PlaneIndex.iMiG_29] = {140.0, -75.0, 90.0} CameraAngleLimits[PlaneIndex.iMiG_29K] = {140.0, -65.0, 90.0} CameraAngleLimits[PlaneIndex.iA_10] = {140.0, -65.0, 90.0} CameraAngleLimits[PlaneIndex.iF_15] = {140.0, -80.0, 90.0} CameraAngleLimits[PlaneIndex.iKA_50] ={140.0, -65.0, 90.0} CameraAngleRestriction = {} CameraAngleRestriction[PlaneIndex.iSu_27] = {1,60,0.4} CameraAngleRestriction[PlaneIndex.iSu_33] = {1,60,0.4} CameraAngleRestriction[PlaneIndex.iSu_25] = {1,60,0.4} CameraAngleRestriction[PlaneIndex.iSu_39] = {1,60,0.4} CameraAngleRestriction[PlaneIndex.iMiG_29] = {1,60,0.4} CameraAngleRestriction[PlaneIndex.iMiG_29K] ={1,60,0.4} CameraAngleRestriction[PlaneIndex.iA_10] = {1,90,0.5} CameraAngleRestriction[PlaneIndex.iF_15] = {1,60,0.4} CameraAngleRestriction[PlaneIndex.iKA_50] = {0,60,0.4} function GetCameraAngleLimits(iType) local p = CameraAngleLimits[iType] return p[1], p[2], p[3] end function GetCameraAngleRestriction(iType) local p = CameraAngleRestriction[iType] return p[1], p[2], p[3] end function SetCameraAngleLimits(iType, hAngMax, vAngMin, vAngMax) local p = CameraAngleLimits[iType] p[1] = hAngMax p[2] = vAngMin p[3] = vAngMax end -- Following values will not be saved in tracks in the current version! hAngleRearDefault = 180 vAngleRearDefault = -8.0 vAngleRearMin = -90 -- -8.0 vAngleRearMax = 90.0 RearCameraPos = {} RearCameraAnglesDefault = {} for i = PlaneIndex.iSu_27,PlaneIndex.iKA_50 do local cockpit_point = CockpitLocalPoint RearCameraAnglesDefault = {180,-8.0} RearCameraPos = {cockpit_point[1] - 3.7 ,cockpit_point[2] + 2.4, cockpit_point[3]} end ArcadeCameraPos = {} ArcadeCameraAnglesDefault = {} for i = PlaneIndex.iSu_27,PlaneIndex.iKA_50 do local cockpit_point = CockpitLocalPoint ArcadeCameraAnglesDefault = {0 ,-8.0} ArcadeCameraPos = {cockpit_point[1] - 20 ,cockpit_point[2] + 5 , cockpit_point[3] + 0} end function GetRearCameraPosition(iType) local p = RearCameraPos[iType] return p[1], p[2], p[3] end function GetRearCameraAnglesDefault(iType) local p = RearCameraAnglesDefault[iType] if p == nil then return hAngleRearDefault , vAngleRearDefault else return p[1], p[2] end end function GetArcadeCameraPosition(iType) local p = ArcadeCameraPos[iType] return p[1], p[2], p[3] end function GetArcadeCameraAnglesDefault(iType) local p = ArcadeCameraAnglesDefault[iType] if p == nil then return hAngleRearDefault , vAngleRearDefault else return p[1], p[2] end end -- LSO local position on the carrier: {x, y, z, rot_Y, rot_Z) -- Note: tracks can't save modified LSO local positions in the current version! LSOPosition = {} LSOPosition["Vinson"] = {88.0, 28.0, 31.0, 0.0, 0.0} LSOPosition["Kouznetsov"] = {81.236, 24.0, 28.497, 10.0, 0.0} function GetLSOPosition(iType) local p = LSOPosition[iType] return p[1], p[2], p[3], p[4], p[5] end dbg_shell = "weapons.shells.GSH23_23" dbg_shell_v0 = -1 Config\View\SnapView.lua (only showing here the changes to Snap[7][13]) Snap[7][13] = {} Snap[7][13]["y_trans"] = 0 Snap[7][13]["x_trans"] = 0 Snap[7][13]["z_trans"] = 0 Snap[7][13]["vAngle"] = -26.802588915303 Snap[7][13]["rollAngle"] = 0 Snap[7][13]["viewAngle"] = 250 Snap[7][13]["hAngle"] = 0.17090886831283 The big change here is to the "viewAngle" = 250 which was origionaly -9.5 ?? Some of these have possibly been made from in game changes to default KP5 view. Note that I haven't made any (that I know of) changes to any of the other aircraft and haven't tried any of them in Eyefinity yet. Try these for yourself but with the usual health warining. Back up your origional .lua's before changing. Here are three screenshots showing the effect. As for a video, I'll try but not sure whether it'll work.

Well I've done something and somehow got it to work with a good FOV and I'm able to pan around without limit. I'm not using the "FOV fix". That kept failing to start. So if anyone wants copies of my .lua files then they are more than welcome. Just don't ask me to change anything LOL. Working (A10 at least so far) in 6028 x 1200 eyefinity with Bezel management on (hence the strange res) Now I can get on with the pleasure of relearning how to operate the A10 and Foxy and Cougar Hotas etc. etc etc. :)

Once again using your Foxy files for my initial setup on FC2. Many thanks Legolasindar