Tornado

me too same issue

Hi Flappie, Update of the stable version (Dec 27 2022) has the same problem. No scoring anymore in the debriefing. Before the update it worked as it should do. It marks your kills. But the update has no kills on A2G kills. I wanted to let you know. Tornado

Thanks Flappie. I wil check the forum from time to time as well as the changelogs.

New data from today. I hope you can find something. A2A gives scoring, but not A2G dcs.log debrief.log track no scoring 18-12-22 17.00 hrs .trk no scoring data flight 18-12-22 ay 17.00 hrs.log

Thanks, here are the files however I saw That there is a time difference in the log files and the track.miz. So I will do another run to have all running at the same time period. But maybe you will find something in this files. test scoring flight.miz.trk dcs.log debrief.log

HI guys still have problems with the no scoring facts in the debriefing after the flight. I destroy targets but never get any scoring when I close the flight. I tried several options and changes in the saved games map. But so far I never found any solution. I have the latest update DCS OB from last Thursday/Friday Dec.15/16 2022. No luck to find the bug in whatever I changed modified. The scoring work in the stable version. You get in red the items you blow up in the flight itself and afterwards you see them in the debriefing. HELP

test scoring flight.miz.trk text was gone but I use 2.8.0.33006 version. Sorry for a late response to busy with funeral. text was gone but I use 2.8.0.33006 version. Sorry for a late response to busy with funeral. I destroyed a Russian tanker on the ground with Mk84's

No scoring in the debriefing indeed. Only when air to ground missions: score 0. Still an issue after the update form last Thursday. Occurred with for last update. ED are you able to respond on this problem. Thanks

Yes that is the solution. Problem gone. But strange that you can start with the full screen. There is no difference so I will keep it that way for the time being. Thank Flappie for your help Tornado

okay here it is. I hope you can find something. I also used my options.lua file from the DCS stable. But same problem as well. options.lua

I have that issue too. Only when I start OB for the first time after starting the computer. I don't have that issue when I start OB for second time etc. Only once after a fresh start of the pc. I can only get into the game in that situation by CTRALTDEL. Not with alt tab. It just stay on the windows desktop an nothing response to the mouse. It freezes more or less. I hear the music playing. Strange situation. Never had that before. I tried with the option options.lua.bak as Flappie suggested. But then I will loose all my settings. That is less briljant. Is there another option. I can copy/past from the lua bak file. But what brings the problem in the lua file that is the question. Please some assistance.

I did the following to get back to my own bindings (HOTAS WARTHOG) for the hornet: 1) Keep your bindings as you made them in the sim before the last update (in my case stored: CWIN (7)/Users/Rob/saved games/DCS.openbeta/config/Input/FA-18C_hornet) 2) Next step go the map DCS Openbeta/Mods/Aircraft/FA-18C/Input/joystick: you will find several lua files. Keep the default.lua in that map and back up all the other you will see in another map or map created by yourself: I made a made called joysticknew. I put these files into this created map: Joystick - HOTAS Warthog.diff.lua T.16000M.diff.lua T.Flight Hotas X.diff.lua Throttle - HOTAS Warthog.diff.lua TWCS Throttle.diff.lua VPC WarBRD + MT50.diff.lua VPC-Throttle.diff.lua Start the game and your own bindings will be back as they were before the update. Be aware that these other files will be back with all upcoming updates as ED will always update missing files or changed files. So this exercise has to carried out with every update. The red/brown highlighted bars are gone now. The conflict in the bindings starts when there are more bindings were attatched to one button. That happens with these new warthog lua files in the default.lua are in this DCS Openbeta/Mods/Aircraft/FA-18C/Input/joystick MAP. Hopes this helps...... For me it did.

What I discovered after the 2.5.1 update is another sound related issue. When you start the mirage on the runway (engine running) or start in the air, you can hear the engine starts up again. It is in the background however because other sound files are louder in the air and on the runway, but you can hear it . Does anyone else discovered this bug? Also when you start the engine it start with the sound of the engine shutdown. When the engine spools up the sound of the spooling engine suddenly stops and other sounds files take over. It runs not smooth however.

What I discovered after the 2.5.1 update is another sound related issue. When you start the mirage on the runway (engine running) or start in the air, you can hear the engine starts up again. It is in the background however, but you can hear it. Does anyone else has this bug discovered?