doveman

I thought it was something to do with 3D actually but you could be right ;)

Well I haven't copied it back, so it's not present at the moment. I think I only created it recently as I read that the maxfps setting had been moved from a file in the DCS installation folder to here. Not really sure why I had the other two lines in there though, although I can't see why any of them would cause a black screen. Do you know where the maxfps is meant to be set now?

After updating to 1.2.4 I just got a completely black screen with BS2 (I saw the briefing/Fly button but that had a blank background behind it as well) (tested with default Instant Missions). I eventually fixed it by renaming my Saved Games/DCS folder so that it had to create a fresh one. Now I need to work out what I can copy back so that I don't have to setup everything again. The Config folder looks OK, certainly Input anyway. I can't see anything wrong in options.lua and network.cfg should be OK. I had created a autoexec.cfg with the following contents: options.graphics.maxfps = 30 options.graphics.render3D = false options.graphics.ScreenshotQuality = 75 and there's a Views/SnapViews.lua (which I think was automatically created). The Missions folder should be fine to copy as well and there's not really anything else worth copying (logs, screenshots) although there is a Scripts folder with export.lua in, so maybe that was the problem.

Phenom II X4 955 running at 3.5Ghz @1.3v. I was running at 3.6Ghz/1.325v with the NB @2400Mhz/1.3v but even though I'm using a TRUE rev.c heatsink and decent fan, it was still hitting the low 50's under load and I've been told running this cpu at 50+ is not good for it, so I've knocked it down to 3.5Ghz/1.3v now. It idles at 800Mhz @0.975v but still the temps are rather high at 30-35c. My other system, with a Athlon II X4 630@2.8Ghz (stock) and Xigmatek HDT-1284 topdown cooler, idles at 18c!

Ah thanks, so maybe the bug is universal and the mouse view mode doesn't work after entering Briefing with it active and then exiting Briefing with either Back or Fly. I didn't note whether I was in mouse view when testing but I'll check. So we only have to remember never to open Briefing with mouse view mode active and not to close Briefing with either of the buttons. :music_whistling: Hopefully this is something that can be fixed then. I use Full Screen mode and don't disable Aero.

OK, thanks for testing. Seems it only affects some people then.

Hmm, strange as JG14_Smil confirmed it. So if you're in mission, press Esc, click on Briefing and then click either the Back or Fly buttons, you can still toggle between mouse cockpit and mouse view with Alt+C? For me, I still have the mouse cursor to click on switches but when toggling to mouse view, it no longer works. Only if I exit from the briefing by pressing ESC is it OK. I didn't realise that IFF wasn't even implemented. Strange that they bothered to make the switch moveable and assign a keyboard shortcut in that case! The switch works for me if I click on it, just doesn't move when I use the keyboard shortcut but hey ho :)

Interesting. Perhaps an update has changed things but I do recall people being unable to even get the Radio menu to appear until they setup and used the SPU-9 key rather than the simple radio key.

I believe the original binding works if you're using Simple Radio mode. If you're using realistic mode, you have to use the SPU-9 PTT key, which I've bound to RAlt+\. The original binding doesn't work on UK keyboards so I had to change it.

Yeah, even the mouse view not working after exiting Briefing with either of the buttons hasn't been fixed yet and that's a major deal as it pretty much forces you to abort the mission. Are you sure there's no need to switch the IFF? It seems strange they'd assign a keyboard shortcut for it if so.

I've had the same problem, although with the mouse cursor visible. I think it generally clears if I press the button several times though.

Not sure if it's new but with 10201 the IFF switch no longer moves. I hear a click when pressing LAlt-LShift-I but the switch doesn't move. When pressing LAlt-LShift-LCtrl-I the IFF switch cover does open/close though.

Ah thanks, I see this tweak doesn't do anything anymore :(

bump

It's the export.lua in your Saved Games\DCS\Scripts folder that you need to add those lines to, if you're using TARS and TACVIEW that is. dofile is just a command so you shouldn't have a file called do or dofile!

I believe this has to go in Saved Games\DCS\Scripts now with 1.2.3.

I read a tip to tweak the network settings a while back so added this to net_types.lua (ADSL.." Custom", 19000*kBit, 1024*kBit), Now in my network.cfg I see connection = { "ADSL 1024", 131072, 32768, so do I just need to edit that to read "ADSL Custom" or do I need to edit the numbers underneath as well and if so, what should I set them to?

Can anyone confirm that the 1.2.3 update hasn't changed the files used by this mod in anyway, so that overwriting the original files with the modded ones won't result in any missing lines that might be important? Is there anyway to deal with this possibility other than asking here every time there's an update? The only thing I can think of is to make backups of the unmodified files from a confirmed OK version and then compare the backups with the installed files after each update, to see if there's any differences. Even then, if I spot any I'd probably have to come back here and ask what to do about them and I have to do this for every mod I use. Not much fun.

Tested with unmodded 1.2.3 and still the same. Didn't really expect it to be fixed as this update doesn't appear to contain any fixes for BS but it was worth checking.

Interesting. I guess it's impossible to ensure the mods don't "break" the update though, which is more of an issue as it's easy enough to disable the mods before updating and re-enable them afterwards to prevent the update messing with them.

Yep, even using JSGME I'm nervous that a file in one of the mods I use has been updated and that re-installing the mod after updating will cause problems. I'm not sure what I'm supposed to do other than manually compare every single mod file with the originals to see if there's any glaringly obvious differences. I could of course just use them and hope but then I'll have no way of knowing if any problems are due to a wrong/outdated setting in one of the files. Guess there's no way round this though, other than bug the authors of each mod to check them to ensure they're still compatible.

Has the export.lua layout changed or could we just backup our 1.2.2 export.lua from Config\Export and then after updating to 1.2.3, copy that to \scripts and Saved Games\DCS\Scripts? Is it actually necessary to have it in both those locations?

Thanks for the video P1KW. It's a good demonstration of the problem.

Old method is unusable for me actually. Central Trimmer method I got just about usable I think by tweaking the TrimmerZone.

I don't have the link but there's a video with the pilot landing on a ship deck using a lot of Trim clicks. How could he do that if it was "jumping all over the place"?