coolts

Sod it. That key ED chose for comms is disputed in too many localised keyboard layouts but 'L' is a constant and one of the free unmapped keys in game. Added that and it all works fine.

Its been 2 years since I looked at TARGET seriously and now I am getting back into DCS, I want to redo my Hog profile for Black shark. The trouble is. DCS comms menu is mapped to '/' in-game I have a UK keyboard and that key for me comes out "#" which is what TARGET sees. Then when I map '#' and run the analyser it produces ' ' ' Crazy, but in the transition from Russia (DCS), French Canadian to me, (UK), something has gone a bit wobbly. I could map the USB keycode...but....as a belt and braces approach, I just remapped comms to 'J'. It appears 'J' is a constant in Russia, Canada and England ;) I'd rather fix this, or when I repost my mk2 profile I will have to ask people to remap keys which I'd rather not.

Cheers. I tried sweetFX after this trick and i think it breaks the ambient occlusion effect. I will try with sweetFX off at the weekend. I had it working last week.

Sorted. edited viewporthandling.lua http://forums.eagle.ru/showthread.php?t=111332

That works, Thanks very much. I had hoped that silly v1.0 phantom monitor would have been fixed by now ;) BTW. How do I stop the in cockpit SHKVAL & ABRIS being rendered now I have them on a separate screen? Doing it twice seems like a waste of CPU/GPU resources.

Has anyone got this working? I’ve gone from 1 to 3 then to 2 monitors as I gave up on SoftTH, etc. and wraparound screens due to fisheye rendering and desk space issues. Coming back to DCS, I rummaged around for my old multi monitor notes and started bashing together a .LUA using ED’s new syntax changes. Ms second monitor is however on the left of the main one and I think that has bamboozled the engine. It seems that ABRIS and SHKVAL viewport’s with negative ‘X’ co-ordinates just don’t render. Is this true? I created a test.lua using the excellent Easy monitor configurator but even that didn’t like windows being dragged to the left. I could set the second monitor as my Windows Primary to set its base co-ords as 0x0 but I don’t want unless I have to as all my other games will start using the smaller screen to appear on.

I cant get it to work with NV inspector either. Do you have to set the options in NV inspector every tie you launch the game? <drmagnumwolf> Can you post your NV inspector settings and any other tweaks you made to get it to work?

As a lapsed DCS flyer, looking at getting their hands dirty again, apart from the patch change logs and wags post “FC3 Changes - 11 November 2012”. Are there any major operational / employment changes to the F-15 that I need to know about? Can I for instance, dust off my old FC2 manual and get going? I noticed the FC2 F-15 profile in TARGET for my warthog once I get my axis sorted. That should do as a start.

hah! tell me if you find out. reminds me of something I drank in a nightclub many moons ago! a hideous effect.

I think that’s a key point. It’s accessible as it’s less scary from the button pressing angle. That potential accessibility is spoilt though by all the LOMAC / Ubisoft palaver. Maybe they could get away from it by dropping the flaming cliff’s / LOMAC name? Probably not as simple as that because of the code base, etc. It’s a shame, and from my point of view, FC is needed in order to provide a “shallow end” of the swimming pool (I presume ED hope that 3rd party will fill that vacuum and they can drop FC eventually). I for one got into DCS via LOMAC and would not have had the patience to come straight at Black Shark without it, but that’s just me. I bought DCS: A-10 as I loved flying the basic A-10a in LOMAC and then FC, following ironhands amazing video tutorials, etc. There may be less button pressing to do in FC but the principles and tactics are the same between the SFM and AFM/DCS aircraft.

Sorry man, I wasn't being intentionally vague. Here's the BMS profile http://www.benchmarksims.org/forum/showthread.php?8147-Morphine-s-Profile works a treat.

SOLD! That sounds amazing! :pilotfly:

use morphine's profile. solves problem one. :thumbup:

I just want to get a feel of how warm the water is before diving in. I’ve got very fond memories of playing cat and mouse in the F-15 vs Fulcrums down low in the mountain valleys of northern Georgia. Popping up and seeing the ‘29’ indicator flash on my RWR and diving low again in gleeful panic, screaming over farms and rivers. It usually ended up with me a fireball, but was so much fun and not an experience I’ve ever replicated in DCS: A-10 or BMS. Warthogs are too slow and the BMS landscape down low just is not capable of offering that visceral heart pounding feel. (Not knocking either sim as I own and fly both). But…. DCS:FASTJET is a ways off and I found my old LOMAC disk yesterday and…….:music_whistling: (I know its a beta. I had A-10 beta from day one so have expectations set accordingly)

yep, after a week of settling in to win 8 I'm not going back. weirdly, my games which used to suffer screen tearing no matter my vsync settings (xcom cut scenes, etc), are now fine, and the memory handling is a lot better. I've got more than one screen so metro has its own monitor basically where I like the tile updates to apps telling me of new email, and news stories, etc. It feels "alive" and my old 7 desktop now looks, well, old ;) and pressing the windows key to flip between metro an desktop is not exactly the hardship that so many are moaning about.

If your running 2-3 monitors, metro makes sense on the desktop. Once you get your apps setup with the live tiles the old desktop feels..............static.......dead..

I got my trackIR working with new beta driver but my TM Warthog keeps cutting out when I run TARGET. Anyone had that? ps. Doubt there will be anymore client service packs for windows. No win7 one planned that's for sure

Cheers Peter. I've read your excellent guides. I've edited the min/max fov and set the default between them so its all good now, (apart form 15fps, but thats another days tweaking ;). ..is all fine The last slight annoyance is that on entering the cockpit, the camera does a slow "Hitchcock Vertigo" camera pull shot. Very annoying. It's done this for ages. Trouble is that it "settles" way back from my new default so when i hit numpad enter the camera jumps. Is this pull back hard coded?

my nose is pressed against the dash ;) This is across 3 screens so basically my middle screen is taken up with the UFC I have edited view.lus and snapviewsdefault.lua but nothings worked so far. I can probably remap trackIR or shift the curve in the axis options but would rather reset this somehow.

Default head position way to zoomed in. Even mapping my throttle slider to "zoom", i have to have it all the way back. Any way to edit the default head z axis? i dont really want to mess with trackIR. Also, 'esc' menu doesnt work, (may be a general DCS bug), as cursor is white

After a night of faffing and nothing working there was a eureka moment in the shower “you’ve got a x64 OS doofus, use the 64bit version of SoftTH”, it works now. YAY. Now one thing before I settle into a serious “getting to know you” session in 1.2.1 with lovely 3 monitor loveliness, (smug ). Do I need to faff with FOV settings? I did in BMS, but haven’t seen anyting in the ED forums about that. Setup is 2 x 24” (1920x1200) flanking a 27” (2560x1440) monitors, full cockpit view.

I cant get on with it. On advanced FM mode i flop all over the place, and the trim is unstable. (not to mention taking off results in rocketing backwards and flipping over without massive trim), Ive had discussions on their forums but not a satisfactory one IMO so have stopped playing until the big patch comes out. going to the beginner/basic FM seems to miss the point to me. And i'm not just being a helo n00b as i can fly the shark pretty well for a capitalist imperialist pigdog

I totally get that. I was just wondering if you bother to get an "x marks the spot" visual reference on your TAD, (and if so, is my suggestion the best way), in the general location of these threats to help you; Thread the needle to get to your primary and out again Take them out if you care to and have spare ordnance A bit like the preplanned threats on Falcon HSD. I find that very useful. ps. 20k? What are you? DCS:747? I can't see the lovely tree shadows from way up there ;)

When Jtac gives threat locations relative to target, do you simply have that in your head when ingressing so you know where to expect trouble or do you mark the general location on the TAD? I was thinking of placing a mark point in the general area given by JTAC for threats, then switching to the steerpoint dial Markpoint mode and either tasking 2nd element with SAM suppression using the datalink or treating these locations as secondary targets once my primary was smoking. It could get a bit fiddly though. And can you still see JTAC red triangle in Markpoint mode, (not at home to test right now).

"reset shkval" (slaps forehead). Yep, forgot about that as well! Bloody hell, when the next DCS module comes out i'm going to need a reverse lobotomy to rememeber everything. :cry: