mkiii

I never bothered with it. I just slide the 2 outer monitors so that the two outside ones sit behind the centre one slightly, with bezels overlapping. The edges match up closely enough to not be a distraction. Or maybe my brain has just become accustomed to it & doesnt see it as much. Maybe its just that I treat the outer monitors as peripheral vision. When I look around with the headtracker, I rarely actually look directly at the outer screens... unless it is to peek at the FPS display or Kneepad.

Thanks chap. That was most enlightning ;) At least we now know the flares do light things up. It's odd that when I zoomed in one it wasn't lighting itself up. I wonder if HDR or other settings affect them?

Not to seem picky or anything, but there are quite a few keys still that cannot be assigned to a button. In fact there are about 90 from a quick count. I can live without quite a few of those, but why we are not be able to assign more useful stuff such as the selecter switch covered above, and more importantly Things that go bang, such as jettison buttons and most importantly, EJECTION SEAT, is a bit of a mystery.

Something similar seems to have cropped up again for me in the Beta (1.5.6.3930.271). Beta now seems to be ignoring the GUI={...} section, and only looking at the UIMainView = line. This is very odd considering the Beta is the same version as the release right now. Release and Alpha are still working fine with the exact same Monitor setup lua.

The flares are dropped, and do light up, but to not illuminate anything and extinguish well before they get to the ground. This is a bug with the flares and not the mission as far as I can tell. You can see them floating down on chutes. Once you pass the target area, select autopilot, and press F6 until you can see them. You will see a glowing sprite on the tip of a cylinder attached to a small parachute. They should be casting light, but notice that they don't even illuminate their own parachute, so there is no chance they will illuminate the ground.

EDIT: I'm still getting this odd problem. The keys will not appear unless I first Try to show them, at which point they may or may not say "No Key". If they do, then usually clicking on the Hide key button followed by another attempt shows them. The difference now is that all owned modules I try, do actually work regardless of the key showing, and all icons are correctly displayed in the main GUI. I have no issue logging in, nor in any other operations. I'm slightly suspicious that everything WAS working great after the last update, fps was better and things (apart from the fubar with the Mig-21 licencing ... AGAIN) were running just fine. Then I got this error just as Windows 10 was carrying out a largeish update without notifying me.

If you do a complete reinstall to clean out potential issues, don't you need to deactivate ALL modules first to avoid using up an activation token? I would be tempted to just try renaming the DCS folder followed by an install, which should leave the registry intact, but give you a whole new set of files. Also, there is the issue that at this time AFAIK, the beta and release are at the same build, so an install of that could be used as a "rescue disc". If you have the same issues in the Beta, then it seems unlikely that reinstalling the release version of the same build would help, but who knows...

I can confirm the headtracker.dll problem. DCS Hangs, waiting for some unspecied svchost process. I had the same problem yesterday after carrying out a repair and clean operation for a different issue, and after spotting this post, and copying the headtracker .dll from a known working install fixed it. It seems odd that it was the repair/clean that caused the problem in the first place. Perhaps this should be on a sticky checklist of things to check if DCS Stalls on startup.

It might be worth noting here too, the one major source of confusion at the start is that your screen res as set in the GUI is your overall screen area, including all monitors that you want to use, and depends on their arrangement in Windows Display settings, whereas your MonitorSetup/viewxxx.lua is dealing with individual viewports, my 5 monitor setup uses 4 for DCS. 3 main ones as one NVidia NView Surround desktop, and a smaller monitor on the end with MFDs stuck to it for instrument output. The 5th is ignored. The main gist of this is that you can set your main DCS screen to be centred wherever you want, on either of your monitors just by entering the viewport size and coordinates / offsets in the above mentioned lua, whereas using the ones that are installed by default don't take into account different sized monitors.

As the title suggests, all previously installed modules suddenly no longer have serials, with "No Key" showing in the Module Manager. On running the DRM Activation selection in Module Manager, the correct keys appear, showing that the module is installed. Clicking on Hide Serial Number button, then again on Serial Number, will make it appear, but after a pause. This will work a few times, but the serial numbers will disappear again randomly, or if Refresh button is pressed. Even when A key is detected, and the aircraft can be flown, it responds oddly, with unresponsive controls (in the 3d world - but ok in control setup) & no engine power. Modules with missing serials have no cockpit & are uncontrollable as if they have not been installed. A Repair has been carried out with no mods, but Licensing issues persist. This is also happening on a Beta & Alpha installs.

Try this http://www.dcskneeboardbuilder.com/

AHhh.. so it's because I have fair hair (well grey) that I'm crap at T/O in these tail draggers then? it's good to know that It's not something I'm doing wrong - just genetics. :music_whistling:

RAF Ford... It's walking distance to my house. Secondly, I want to see the land bridge that joins East Anglia with Continental Europe at the extreme North of the Map. I thought Doggerland was submerged 15000+ years ago...

[EARNEST] Having said that, I would like to see a more contemporaneous FW 190 A-7 or A-8 in the sim to see how it stands up against the Mk IX... Then you too can be "Pips" Priller during the D-Day landings. [/EARNEST]

Maybe I should have added a /sarcasm ... sarcasm/ block around the text... or half a dozen smileys at the end?

I always assumed they were like the AI pilots, ie almost infallible. Must just be my crappy skills that mean an IR missile=death ;) I'm no expert, but anyhoo... Having just spent an age dealing with RL Simulation of FLIR, and getting RSI in the process, I can guess that judging by the amount of time and data that was involved, and bearing in mind that this is probably not as complex as what is going on in a missile seeker head, that if they were using anything approaching real world figures, then I would expect to see a lot of data clogging the install folders just to deal with the subject. As mentioned above, there is a lot more going on than just heat signatures. Different materials heat and cool at different rates, and are affected by ambient conditions in different ways. I also wonder how realistic the cooling of IR missile heads modelling is. Being a ground pounder by choice, I haven't read the manuals much on the subject, but I do know that IR missiles can have a quite limited shelf-life once they are activated, same goes for battery power on some missiles. I'm sure there are some knowlegable people out there who can shed light on this.

As far as the Normandy map & the English Channel is concerned, fuel range of the Spitfire won't be an issue, since all BF109k and FW-190D owners will have to wait about 5 months after "D-Day" for their aircraft to start entering service before they can start using them on the Normandy map (if you want to be realistic). Until then the Spits can all just move over to France and chill out in the enemy free skies, unless someone releasea a FW 190A8 or a BF109G in the meantime.

If you spin the wheel by dragging with the mouse, it goes much faster than when you use buttons, keystrokes or the mousewheel. Just remember that the wheel will go 1 full revolution either side of neutral. At Max, neutral and min, the hole in the wheel is always at the bottom, so it's eay to see where you are.

One other thing that helps me in the final stages is if i "cheat" and apply about 2 or 3 clicks (200-300 psi?) brakes before landing. Note that this is only possible if you have set buttons for "Wheel Brakes" (the lever on my stick), "Wheel Brakes INCREASE" and "Wheel Brakes DECREASE" buttons. A touch of the brake lever overrides the inc/dec setting so it is pretty safe to use. Oh and I found another nice set of notes on takeoff & landing procedures for a Spit that I havent seen before, http://forum.keypublishing.com/showthread.php?72714-SUPERMARINE-SPITFIRE-Take-off-and-Landing-Guide

It's not just me then ;) For me, the biggest bit of advice was to memorise the "on ground picture" and trim to get as close to that in the final floaty stages before touchdown. The other thing that helped me a lot was to never ever try to do a straight in approach. You just cant see the runway for long enough. Always do a curved in approach left or right depending on wind conditions, and always be prepared to counter torque effects. I still scrape my wingtips quite often though, but it's usually because I have overcontrolled. The fact is, unless you have a 3 foot long throw and realistic weightings on your stick, it really just comes down to muscle memory, 'cos we are trying to control a sportscar with a toy stering wheel. Either way, it's a lot cheaper than a go in a real Spitfire isn't it?

:music_whistling:We stand corrected.

Isn't that the area of the Caucasus where the graviton flux field is distorted? I'm sure I read about it on some wikipedia page or other.

perhaps what might be a little confusing is the blurb referring to the WWII Assets pack / bundle. This just means the extra AI and placeable models that will be available to populate the map, such as the WWII tanks and vehicles. Although this is just a terrain area, I do hope that some restriction can be placed on the "Create fast mission". A parameter that can be used to restrict auto generated assets to the correct era for the aircraft selected would be nice. The other day I tried one with the F-86 selected without thinking and immediately got blown out of the sky by a pair of SU-27...

Assuming that it isn't just overheating or some other finger trouble, I had a similar problem in the spit a while back. What was happening seemed to be related to the Headtracker device turning off bug. Sometimes some USB related glitch would turn off both mags, which were mapped to switches on my throttle! The only indication was that the switches had moved, and if caught in time, they could just be turned back on, so it isn't beyond the realms of possibility that this IS a magneto related problem (sort of).

If the X55 uses the same profile software setup as the X-52, then can't you use a profile with ranges set so only a small portion of the range of movement at either end of an axis elicits a keystroke? I seem to recall that this is how I did it before I moved to a TM WH. Or enter a few ms pause inbetween key down and key up events. Either way, it means using a profile.