Ebs

There is! Hit right shift P to show your pilot and you can see his kneeboard there. If you want to mod it, take a look at how TurboHog did it for his awesome JTAC mod... http://forums.eagle.ru/showthread.php?t=93228&page=13 ;)

Here's one I've been working on...I guess you're the first to see it! :) JSGME compatible. (of course ;)) Ebs KA-50 SHVKAL Mask.zip

http://www.downforeveryoneorjustme.com/http://proactive.star-force.com/ Great site btw. (downforeveryoneorjustme)

Mod now on ED site - http://files.digitalcombatsimulator.com/en/273485/ Edited first post...

ModMan is more hassle than it's worth imho. TheMoose, check this out - http://forums.eagle.ru/showthread.php?t=98607

TapRoot, that's a shame man. This isn't aimed at you specifically btw, as you got it preowned and saved some cash in the process...BUT... Everywhere I only see posts from G940 owners complaining about how crap it is...Worn pots, Hysteresis debacle etc. etc. The Warthog gets some flak for how expensive it is...but the POS G940 almost costs the same...There's post after post of problems regarding this stick and people STILL buy it...it amazes me... It's like people want to convince themselves that all these problems won't happen with their G940...It's a turd and Logitech should be ashamed for releasing it. I read somewhere that it was just supposed to be a FFB stick on it's own...but then they decided include the throttle and pedals to justify the price...this means the throttle and pedals were made with the absolute cheapest components they could find...and no doubt the stick components also suffered as a result. I've yet to see a single post where a G940 owner has said 'this is the best HOTAS I've ever owned' now compare that to all the TM Warhog 'gushing' posts. There's more chance of Fighter Ops being released than me using a G940. It's shocking. Rant over, sorry.

Hey, brand new to Target myself but I'm pretty sure it's not possible to run the Warthog as two seperate devices when using the scripting. As far as DirectX, this limits it to 8 axes and 32 buttons...No way around it I think! The stick has 19 buttons alone...so assign those then use up the remaining 13 for the throttle. But after that you need some keyboard shortcuts. I'm in Vienna too btw :D

Sounds like worn pots :( How long have you had the G940?

...Is that I didn't get them sooner! Haha! ;) Seriously though, this thing is awesome. I had an X52 (non pro) before and a MSFFB2 before that...But the Warthog? Wow. I'm not knocking the X52. It served me well and I had it set up exactly how I wanted it, but after two days with the Warthog I doubt I could ever go back to the 52. One thing's for sure, the Warthog takes some getting used to. The first flight felt like I was arm-wrestling Schwarzenegger and nothing was where it was supposed to be! (like on the X52 I mean!) and I felt myself overcorrecting everywhere. I didn't expect it to be so sensitive. It almost feels like it's force sensing, honestly. The Saitek programming software is pretty deep, but I didn't expect the level of programming available via target. Of course, everything's plug and play with the 'hog but being a developer in my day job, I took a look at some Target stuff and it blew me away. One of the reasons for getting the Warthog was so I wouldn't have to do so much tweaking...But seeing the possibilities with Target threw all that out the window :) As for the pedals...can't complain. I had a set of CH Products pedals years ago but I couldn't really get over the fact that they were so close together. the Saitek's feel so much better in that regard. Quick deadzone setting and invert for the toe breaks in DCS and all is set. In short, I can't be happier.

Just double check for me Mastiff. load DCS via the MP icon...join a server...join a plane then exit server. if you see Debriefing screen then all is well.

Are you sure about this Mastiff? The mod only updates the logbook when you see the debriefing screen. If you start MP directly then exit, you won't see a debriefing screen so your logbook won't update. And yes, no more 'initiator' changing. it's all automatic now :)

Thanks guys :) Basically the last aircraft you joined is tracked.

MP Logbook mod 1.2.3 update here - http://forums.eagle.ru/showthread.php?t=102188

UPDATED FOR 1.2.4 Hi all, Decided to post a new thread as a continuation of this one - http://forums.eagle.ru/showthread.php?t=101568 This Mod enables the in-game Logbook to track your Multiplayer flights as well as your Singleplayer flights. It's a simple install. REQUIRES NO MANUAL FILE EDITING...Either use JSGME or overwrite your files in the DCS World directory (remember to back up the files you're overwriting) After install, start DCS:W via the launcher and click Multiplayer, after joining a server and flying a plane. Click exit to exit the server...at this point the Debriefing screen will load and your logbook will be updated. Just like in Singleplayer... Here's a screenshot from a mission I just flew on the 104th server... There are some requirements... 1. Your logbook name and Multiplayer name must be the same. 2. you MUST start Multiplayer via the launcher. 3. when flying Multiplayer, stick to ONE plane...fly your mission/die/eject/land..even respawn...but YOU MUST STICK TO ONE PLANE...then 'EXIT' to the debriefing screen to update your stats. You can then rejoin the server and chose another plane. This is neccessary to due to how DCS:W handles player slots. I did have the mod tracking multiple player planes during a session, but if another player takes your slot in the same session, their stats will be added to yours. I'll upload the mod to Userfiles but in the meantime, DOWNLOAD HERE

Mastiff, the MP Logbook is buggered in 1.2.3...don't use it. Although, I updated it today to work with 1.2.3...so lookout for a release soon. ;)

Guys, a potentially terrible thing has just dawned on me regarding the BETA version of this mod. I'd enabled a workaround in which to get the stats for multiple planes during a multiplayer session. It basically uses the same idea as the single player process. Each plane has a unique id, so I was simply tracking which planes were flown by the player and updating the stats for each plane via the debrief.log that's written after every mission. Now, this is the problem...what happens if you leave your slot and another player takes your plane? That's right, their stats are incorporated into your logbook. The in-game logbook was never designed to track more than one plane in a session (as it's basically a single player logbook) so there's no inbuilt routines for checking who is in which plane when it comes to updating the stats. I'm pretty sure the 'final' version of this mod will revert back to the 'one plane only' system. You'll have to make sure that when you join a server, pick a plane and stick to it. You can takeoff/land/refuel/rearm...even despawn and respawn as long as you keep the same 'slot'...you just have to make sure you exit the server when you want to change planes...update your logbook then rejoin the server and change planes. This has the added effect of showing you a proper debriefing screen (it won't be blank anymore) and updating the logbook will be more efficient. Sorry if I disappointed anyone. But I'd rather do this than have people coming to me asking why they have 30 friendly kills in a mission because they changed planes while a newbie took their slot and carpet bombed their own FARP. Thanks for understanding ;) Ebs.

Sorry to hear that Mastiff, I'll test a little more with FC3...Can you tell me a little bit more about when the crashes occur? Are you sticking to one plane? Changes sides? etc. With 1.2.3 being further delayed I'll have a bit more time to polish this off :)

Quick update... I'm pretty sure it's fixed now. The latest update of this mod doesn't use the export.lua anymore so it'll work on servers like the 104th... Let me repeat, the 104th guys are incredibly nice and supportive. Total gentlemen.

Gizmo, read the first post again...between the EDIT EDIT EDIT EDIT lines

fangav, unfortunately it is a fact. Right now the export.lua integrity check is basically a blanket ban on all those incredible mods. However, I made a post on their forums and they're nothing but gentlemen about this whole thing. Maybe we can work something out. I really hope so.

Me too! but in the case of the 104th server you'll have to do play in that environment without your logbook updating. ...and without Helios, iControl, TARS etc.

U,FO?

HiJack that's exactly what I tried to do with the first release of this mod, and as you say, it doesn't work. The DCS bug that doesn't tie pilotnames in the stats make it unreliable. The new export line that exports the playerplaneid does fix this 100%. ah well, after a bit of reading it looks like this mod is a no go for the 104th server. They check the export.lua which effectively bans my MP logbook mod. It also bans... TacView TARS iControl DCS Helios and any other mods that require the use of export.lua it seems a bit heavy handed of them to do this on the off chance that someone uses one or more of these mods for the purposes of cheating, but there you go. I'm more of a COOP than PVP server man myself so it doesn't really affect me much. Maybe someone can get it touch with the 104th guys and maybe convince them to change their minds...in the meantime though there are other servers :)

Thanks for the update. In my opinion they should be checking the export/config.lua this contains a true/false switch which enables exporting of 'sensitive' data. When set to true you're able to export the entire sim data. Positions of all units etc. Tacview uses this true switch for example. A config of false only allows the sim to export data relating to the players own plane. Like I said, I purposefully used an export command that only deals with the player plane id so the config remains false.

That is a shame. I purposefully make it so the mod doesn't use any functions that could possibly be used for cheating. The only export command that is used is getting the players plane id. Even the export config doesnt require the 'true' switch. I suppose the 104th has a blanket ban on mods though? :(