Ebs

oh c0ff you big tease! ;) obligatory "OMG WHERE IS 1.2.4?!!!!ONE!!SHIFT+1" btw, Just realised from your sig that it was you who I emailed. hi :)

Mastiff, I saw a pattern of it happening with the P51 too. But it seems that's its purely random with what AC it affects...I'm not sure if it's a mission issue or a DCS Engine issue

Mastiff that's a bug with dcs not outputting pilot names in the log (a dev confirmed it) try different servers until i release the new version.

Hijack the original version reads the initiatorpilotname from the log. Looking at that log it shoulgd have aded an ejection to your su27. Didn't that work? Hang tight new version is coming that is rock solid :)

Btw ctrl+f is a very handy shortcut to know. Is it working now Mastiff?

Zmey HS is the man to ask in that regard.

Magic, what are you using to edit the file? Make sure you use Notepad++ just to be on the safe side. If it still doesn't work either send me an email or wait a couple of days for the new version :)

+1 btw, I've had quite a few emails from people offering to help with the BETA version. Thanks very much guys! all being well I'll release it properly after 1.2.3 comes out...depending on when that is! :D One thing I haven't tested is Combined Arms. it's the only module I don't own...so I'd appreciate some feedback about that too. Once again, just remember to give the sim some events to update your logbook with and all will be well. Cheers.

Wow! this thread saw a few replies today, thanks guys! I saw the discussion regarding the "." character in a callsign. After further testing I can confirm that the "." makes no difference whatsoever! "104th.Taproot" will work just as well with the "." as without. Here's the thing, the logbook needs events to update the stats...simply joining a server in airstart and flying around for 5 minutes doesn't give the logbook enough info to update. One of the required events is taking off...this hooks an event. In my testing I set up an airstart mission...joined the mission, fired a burst from the GAU and flew for a minute or so...this firing a weapon also hooks an 'event'...btw, this is all true for Singleplayer too. you probably just weren't looking for it! :) Install the mod and don't think about it!...just join a server and fly as normal...take off, kill some stuff then exit and check your logbook. The only thing you'll have a problem with is if the debriefing screen doesn't show your Callsign...then the stats won't log...but that's fixed in the new BETA too ;) Btw... This isn't true. "." is no more recognized by 'the coding system' as the letter "E", especially when it's declared as part of a string. if it was part of a number then that'd be a different story...Even reserved symbols can be a part of a string if we use escape characters.... :music_whistling: And your welcome. ;)

Here's where I'm at guys. After a lot more work on this, I've managed to fix the problems. The mod now... 1. requires no editing to install. 2. Always tracks your plane in Multiplayer. 3. Tracks ALL your planes in a Multiplayer session! no more disconnecting in between planes to update your stats What I would like though is a few people to test this new BETA version. The only requirement is that you fly a few multiplayer sessions (with different planes etc.) and provide some feedback for me. Drop me an email at typingoutloud@gmail.com and I'll send you the BETA version

Ricardo, can't wait for this! TurboHog, Reapers pic is a real picture! :D

Yes please! Very nice :)

Otto, if you email your logbooks to me at typingoutloud@gmail.com I'll try and sort it out in the next hour.

Thanks guys :) Glad it's working out for you! Just open the old logbook and the new logbook and compare them. it should be pretty simple. All your flight time etc. is listed in seconds. Just add the old stats to the new stats and save the file ;) Yes, you need to 'host' the mission as a LAN mission...Multiplayer/new server/LAN...load your mission...play it...exit. Stats logged.

Yes, the mod doesn't affect your current stats.

http://forums.eagle.ru/showthread.php?t=101568 Can I officially name you guys as disciples then? ;)

EDIT: UPDATED THREAD HERE http://forums.eagle.ru/showthread.php?t=102188 Hello, Well after a week of spending almost my entire free time on getting this to work, I can finally say I've done it. The mod allows your Logbook to also track all your stats in Multiplayer sessions. Both as host and as client. Installation is simple. Either use JSGME or overwrite files with those from the zip. There are three simple steps to take before it'll work... 1. open my me_debriefing.lua file and find this line iInitiator = "Ebs" CHANGE "Ebs" to your multiplayer name. 2. make sure your callsign in your Logbook is the same as the name you use online. 3. Always run every multiplayer session via the launcher! Once the mod is 'installed' you'll see the debriefing page after every multiplayer session, just like in singleplayer...your logbook will also be updated with your kills/flight times/ejections etc etc. exactly the way it is with Singleplayer. There are a couple of issues... 1. In a multiplayer game, the stats for the first plane you fly will be tracked..if you crash/eject/die then join another plane. your stats for the second plane won't be updated...The way around this is to treat every multiplayer session as a singleplayer game. when you lose your plane, simply hit exit back to the debriefing screen. then rejoin the server and choose another plane. 2. Occasionally, the game doesn't assign a PilotName to a plane..I've seen this happen with the P-51...You exit to the debriefing page and the list of events for your plane lists the pilot as 'Pilot #32' or whatever...the game doesn't know it was you who was flying so won't update your stats. I'm not sure if this is a game issue or a mission design issue, but I've only seen it once or twice in the last week. That's all. Have fun and if you like my mods I'd really appreciate any PayPal donations to typingoutloud@gmail.com Cheers... Ebs. Now if you'll excuse me, I've got a weeks worth of flying to catch up on! ;) EDIT: UPDATED THREAD HERE http://forums.eagle.ru/showthread.php?t=102188

Yeah that's what I said! ;) Sobek, this isn't aimed at you it's just general information: "launcher" contains the actual debriefing page, logbook and code to update the logbook. This code is run when the debriefing page loads...which is does after every SP mission. When you run a mission from the launcher, the DCS.exe runs. When the mission starts, DCS.exe starts generating the log file. Upon mission ending "exit...closing dcs.exe" this log is written as Debriefing.log in your Documents/Saved Games... etc. folder. You can see this file after an MP mission too. The main difference is, when you exit an SP mission, Launcher reloads, and you end up at the debriefing page which updates your logbook using the Debriefing.log. When you exit a MP 'mission' the launcher reloads at the main menu...thus, no logbook update. Here's a test if you don't mind getting your modding fingers dirty ;) goto DCS World\MissionEditor\modules\MainMenu.lua and find a block of code in that file that looks like this... function buttonMultiplayeronChange() base.START_PARAMS.command = '--net-mode gui' base.START_PARAMS.returnScreen = '' if base.MapWindow.isCreated() then base.MapWindow.close() end Gui.doQuit(); end There's a "returnScreen" statement there...and it's blank. What I did was turn that statement into base.START_PARAMS.returnScreen = '[b]track[/b]' This tells DCS World to return to the track(replay) screen after ending an MP mission. This also has the side effect of returning us to the debriefing screen first! Try it out.... Remember you must start an MP mission from the launcher ...join a plane. do some stuff in it...then click 'exit' to close the session as normal....Launcher will reload and display the Debriefing screen...you'll see all the stats from all the players on the server you were just on...But, there's no player data at the top (player name aircraft etc) so the logbook won't update....But, it's a start ;)

That's not exactly true. Single Player and Multi-Player both use DCS.exe and DCS:W exports the stats for every mission as a log file (SP and MP) The problem is, the logbook is only updated when there's a return to the debriefining page contained in Launcher.exe I modded the files a while back to make DCS World show a debriefing page after every MP game where you could see all the stats from the MP session. This meant you had to launch multiplayer from the launcher every time. This way, stats were logged in the logbook but not in all cases. The engine had trouble figuring out the Players Plane. In short, while it worked to some extent it was a bit messy. I might take another shot at it now I know more about what DCS exports...I reckon it's possible to mod in a MP logbook somehow. schau ma mal ;)

Sorry about that last post! Here's Soglagun [TbilisiMilitary] = { runway = { ['13-31'] = { side = { ['13'] = { { type = BEACON_TYPE_ILS_FAR_HOMER, callsign = "TB", frequency = 1050000.0 }, { type = BEACON_TYPE_ILS_NEAR_HOMER, callsign = "T", frequency = 250000.0 }, ILS:frequency(111.75, 'TIB', math.rad(3.0)) }, ['31'] = { } } } }, airdrome = { TACAN(21, 'X', 'SOG', {x = -318876.5, z = 903131.1}) } }, :)

Nice one Paul! Great to see someone fleshing out the file! As Paul also mentioned there's a problem with ILS on more than one runway. It also doesn't seem to be possible to add ILS to Gelendzhik (crashes the mission editor) Paul, I did manage to fix Soglagun though.... If you look in Beacons, it's listed under TbilisiMilitary = {} and has a blank entry....just give it a runway and Airdrome block and assign your frequencies. 04-22 runway btw :)

Speed, I could only get it to guide on the KA-50's laser. That was as far as I got!

.miz is a regular zip file. not familiar with .mis but rename it to .zip and give it a try. it can't hurt!

Alfredo, the charts at http://aviadocs.net/aip/html/eng.htm say otherwise. There's a VORDME at Krasnodar - Center a VORDME at Mineralnye Vody and a DVOR at Sochi Adler. Funnily enough I can't find any info for URKH, URKW or XRMF at that site. I realise the mod is kind of 'proof of concept' at this point, but if I can encourage a couple of people to get involved with modding the files then we can work on making it more realistic.