fjoesne

Can this be fixed with the mission-planner somehow?

I can confirm this.. I haven't reviewed the attached trk-file, but I guess it is the taxi-jam you are referring to. bummer :cry:

Thanks!, I figured it out once I installed notepad++, i also had the MFCDs in the same brackets as viewports.

Is there an updated guide out there somewhere? I've made this work some time ago, but now it simply does not do it. I'm guessing there has been significant changes since that time. I used to get the SoftTH logos up during the loading screen but now i get no indication as of what goes wrong. I dont know where the logfiles are supposed to go if i enable debug-mode, anyone know? If i can't see what goes wrong this is pretty much a :wallbash: .

I cant get this config to show up in the pulldown menu under options. I'm guessing there is some syntax-error here.. Is there a logfile for things like this i can tail? would be so much easier to debug things like this :/ _ = function(p) return p; end; name = _('Tripple with MFCD'); Description = 'fjoesnes'; Viewports = { Left = { x = 0; y = 0; width = 800; height = 1280; viewDx = -1; viewDy = 0; aspect = screen.aspect / 3; }, Center = { x = 800 y = 80; width = 1920; height = 1200; viewDx = 0; viewDy = 0; aspect = screen.aspect / 3; }, Right = { x = 2720; y = 0; width = 800; height = 1280; viewDx = 1; viewDy = 0; aspect = screen.aspect / 3; }, LEFT_MFCD = = { x = 800; y = 0; width = 512; height = 512; }, RIGHT_MFCD = { x = 2208; y = 0; width = 512; height = 512; } } UIMainView = Viewports.Center

This is the default 3 display setting: { Left = { x = 0; y = 0; width = screen.width / 3; height = screen.height; viewDx = -1; viewDy = 0; aspect = screen.aspect / 3; }, Center = { x = screen.width / 3; y = 0; width = screen.width / 3; height = screen.height; viewDx = 0; viewDy = 0; aspect = screen.aspect / 3; }, Right = { x = screen.width * 2 / 3; y = 0; width = screen.width / 3; height = screen.height; viewDx = 1; viewDy = 0; aspect = screen.aspect / 3; } }Changing this to the following crashes the program at start. (the classic just not starting with no error message issue) To make use of this setting I have to start the game, change the config to this while it is still running and then start a mission. Feels kinda unecessary if you ask me. The reason i have to do it like this is because i have 2 different displays. 2 smaller displays in portrait mode on each side of the main display. Viewports = { Left = { x = 0; y = 0; width = 1050; height = 1680; viewDx = -1; viewDy = 0; aspect = aspect.ratio / 3; }, Center = { x = 1050; y = 0; width = 2560; height = 1680; viewDx = 0; viewDy = 0; aspect = aspect.ratio / 3; }, Right = { x = 1050 + 2560; y = 0; width = 1050; height = 1680; viewDx = 1; viewDy = 0; aspect = aspect.ratio / 3; } }

Nice, clearing cookies did work! :D What about the discount code entry?

Is it just me or is the online shop for DCS completely dysfunctional? Whenever I try to buy a module i get the message that i have to register or log in. When I do log in (again) the same thing happens. It is like the E-shop is not connected to the site otherwise. Also, where to I enter discount codes etc?

If I start DCS and run a mission it works just fine with my multimonitor setup, but when I end one mission to start another DCS changes my setup so that every monitor is mirroring each other. When I quit DCS to correct this problem I have to reset all my display to extend the desktop again. Only workaround I have so far is to quit DCS every time I want to do another mission. This was no problem prior to updating to 1.2.5. Anyone know of a better workaround? My setup may be somewhat complicated because I have 2x24 inch running at 1200x1920 and one 1650x1050 in the middle. I have the smallest one in the middle because I have an iPad running A10 Virtual cockpit with MFCDs and some extra interface below the small screen, while the larger displays give me a peripheral. This is why I do not use eyefinity etc because it requires all displays to run the same resolution and lower resolution on the 24 inch displays are no good. Other info: HIS radeon HD 7870, windows 7, DCS 1.2.5, A10-C

Yes, the hat movements in the menu indikates that the right directions are linked to the TMS but to FORWARD and AFT instead of UP and DOWN, I've read somewhere that this is basically the same (?)

I am just going through the trainingmissions and under navigation i get no response from either the keyboard nor the x52 joystick when asked to press and hold the HOTAS TMS Down (or LCTRL + DOWN). Is there some setting in the keyboard combo that has changed regarding this? I can understand something beeing wrong with the stick configurations but shouldn't the keyboard combo work in any case? I cannot get this thing to work please help! I'd like to get through the trainingprograms before i start actually doing missions:)