Stacker

As per the title, voice recognition is a (free) built in component of the Windows operating system. Why not be the first vendor to fully embrace it and make it a first class option within DCS? Instead of having to use 3rd party voice apps (which simply use the free API to send key strokes), if we had an additional 'Voice' option when configuring our control maps it could provide a whole new dimension to controlling the game.

@SharpeXB, @Sierra99,@QuiGon - Yes, you are all correct. The current 9-line attempts to accurately model what a real JTAC would do and that's great. However, my point is that it would be nice to have the option to reduce (not replace it). Rather like the simplified communications option. Some would like full fidelity, others would like a simplified way of doing things. I think the current 9-line flow actually breaks the immersion because of the menu's etc.. rather than enhance it.

Would be nice if we could have an option to reduce (simplify) the length of the 9-line communication script (and just basically get the data msg). It quite often becomes a tedious and repetitive experience (especially after the preamble and the JTAC replies with 'no tasking available' etc..) I'm thinking along the lines of ... "Hawg one ready for tasking" "Hawg one tasking available, prepare to receive 9-line", I'd then get the data msg at that point. Like I said, not a replacement but an option on the settings page just to reduce the length of the call.

Can you OC your CPU? Does that have any effect? I normally push mine up to 4.6GHz for DCS/FSX.

Are you running this in true full screen mode? (i.e LALT+ENTER after you start DCS)

But what is the problem? Low GPU usage isn't an issue if your gaming/sim experience is good for you. Do you have low FPS, stuttering, corruption?

Got any devices attached to your rig? Try pulling them all out (including your hotas/joystick) and see if you can get in game. Also, check your windows logs in the event viewer (application & system) - any errors in that?

Done the repair, rebooted and.... all is good, weekend is now sorted! Thanks guys. :)

Just spun up the latest hotfix. Went full screen mode and everything went bad. Win 7 + 355.98 NVidia drivers.

Had similar(ish) issues myself initially. My own silver bullet that seems to have solved all my jittering and made things run buttery smooth were as follows - - Used NVIDIA inspector and deleted the existing DCS profile - Created a new one by adding the dcs.exe from the open.beta location - Set the following --- Triple Buffering ON --- Vertical Sync Smooth AFR ON --- Vertical Sync Tear control STANDARD --- Vertical Sync FORCE ON - Ensure game is in full screen mode (LALT + Enter) (I have to do this every time I enter the game) - Turned VSYNC off in the game From that point onwards I've had nothing but joy with things. YMMV. Cheers.

Yes, I'm aware of using tracks but it's not ideal, that's just a workaround. If we had a dedicated option that would play through a simple pre-scripted scenario that also contained accurate benchmark stats at the end it could be used not only to improve my system but also give indications to other people about their rig setup etc.. For example, if I knew object count was a factor in my rendering speed, I'd lower the clutter/draw distance etc.. What about my AA setting, is that affecting my frames etc.. Could I sacrifice some image quality for performance. All of this is possible using tracks but again it's not the right tool for the job. Cheers.

+1 on this - lovely night light cockpit effects with the F15 but limited by the fact you can't see a thing outside at night. Is that realistic though, do F-15C pilots have NVG capability?

I think we really do need a benchmarking mode. Something that would replay either a static view or a scripted flyby on rails that would allow us to tweak and test our settings to see what effect the changes made to FPS etc..

Similar crash. Attached zip with log/dmp/crash files. Also included the fast mission generated miz file. DCS-Crash.zip

I just did something similar ready for the Beta - no issues really. Just installed the base DCS World Beta, started it up and went to the module manager, logged in and then installed all my modules. Because most of the data was already on disk from the released version the installation just copied most of it over.

edit your network.cfg file in your 'Saved Games' folder and set the disable_events to true, i.e disable_events = true I believe that will stop all the announcements in your MP games (it certainly used to anyway).

From my developer point of view, I'm looking forward to getting under the hood with DCS2. In particular I wonder what goodies (if any) we are going to get with the scripting environment. I notice that Wags mentioned mission editor improvements, it'll be interesting if that also translates into scripting API updates etc..

Hi, This may be a bug or I've not configured things correctly - after about 10 minutes of flying I notice that my HSI is completely off when compared to my wet compass. It also starts to rotate very slowly so it becomes impossible to use. The course deviation is still accurate (when I'm flying an ILS for example), it's just the heading that's wrong. Is there a way of resetting the HSI heading to align it back to the wet compass/mag north?

Thanks for the update. I picked this module up last night as part of the summer sale, it's a really impressive aircraft with lots of things to like and I'm glad I bought it. You guys have done a fantastic job in modelling and systems implementation! Really looking forward to the AFM and CC version!

Just had a quick fly over the same place to check it out, looked fine on my rig. Looks like the ground texture has leaked through, very odd. Was it a new mission file or an old one?

I've counted all the rivets on that model and unfortunately it's missing 3 of them so there's no way I'm buying this junk until ED fix it.

Hi, (This thread probably needs to go into the mod branch etc..) I messed about with the export stuff about a year ago and produced some test code. I have no idea if this stuff still works with the latest version of DCS (or if the folders paths are still correct). Anyway, this might get you started - the script just outputs various bits of telemetry (pitch/bank/yaw) to a file on your machine. You would have to tweak it to output to a socket etc.. Create an Export.lua in your Save\DCS\Scripts folder and add the following code local default_output_file = nil function LuaExportStart() default_output_file = io.open("./Temp/Export.log", "w") end function LuaExportBeforeNextFrame() end function LuaExportAfterNextFrame() end function LuaExportStop() if default_output_file then default_output_file:close() default_output_file = nil end end function LuaExportActivityNextEvent(t) local tNext = t local HSI = LoGetControlPanel_HSI() local t = LoGetModelTime() local name = LoGetPilotName() local altBar = LoGetAltitudeAboveSeaLevel() local altRad = LoGetAltitudeAboveGroundLevel() local pitch, bank, yaw = LoGetADIPitchBankYaw() local engine = LoGetEngineInfo() if default_output_file then default_output_file:write(string.format("t = %.2f, name = %s, altBar = %.2f, altRad = %.2f, pitch = %.2f, bank = %.2f, yaw = %.2f, RPM left = %f fuel_internal = %f \r\n", t, name, altBar, altRad, 57.3*pitch, 57.3*bank, 57.3*yaw,engine.RPM.left,engine.fuel_internal)) end tNext = tNext + 1 return tNext end Create a 'Temp' directory in C:\Program Files\Eagle Dynamics\DCS World' folder (this is where the export.log file written) When I run this in single player I then get a file with the following telemetry data (current output rate is one row per second). t = 0.00, name = New callsign, altBar = 2000.09, altRad = 1465.27, pitch = 6.36, bank = -0.00, yaw = 380.10, RPM left = 81.801552 fuel_internal = 3775.000000 t = 1.00, name = New callsign, altBar = 1999.63, altRad = 1417.33, pitch = 6.07, bank = 0.01, yaw = 20.27, RPM left = 81.803558 fuel_internal = 3774.959717 t = 2.00, name = New callsign, altBar = 1998.34, altRad = 1397.08, pitch = 6.00, bank = 0.05, yaw = 20.27, RPM left = 81.808098 fuel_internal = 3774.797607 t = 3.00, name = New callsign, altBar = 1996.51, altRad = 1367.13, pitch = 5.72, bank = 0.07, yaw = 20.28, RPM left = 81.811615 fuel_internal = 3774.533203 t = 4.00, name = New callsign, altBar = 1994.15, altRad = 1336.53, pitch = 5.48, bank = 0.09, yaw = 20.29, RPM left = 81.815186 fuel_internal = 3774.189453 t = 5.00, name = New callsign, altBar = 1991.27, altRad = 1305.31, pitch = 5.29, bank = 0.11, yaw = 20.30, RPM left = 81.817825 fuel_internal = 3773.783691 t = 6.00, name = New callsign, altBar = 1987.95, altRad = 1289.69, pitch = 5.11, bank = 0.13, yaw = 20.31, RPM left = 81.819679 fuel_internal = 3773.329346 Again, I have no idea if this stuff still works in the latest build of the engine. Good luck!

When doing reinstalls etc, don't forget to deactivate your existing install first. This will preserve your activation keys.

Will be interested to hear how you (and indeed anyone else) gets on with the new card. I'm on the verge of pulling the trigger for a complete new rig, the only thing holding me back now is the lack of 980 availability in the UK. Once supply ramps up then I'm all in. Also, if anyone else out there is running other stuff like A3 etc.. would be interested in your feedback to see what difference the new cards are making.

I just tried it and it works ok. Went from 000X right the way up to 129X, (via 16X) etc.. Also tried looking at it from different angles via track IR and all seems good to me. When you move your mouse over it do you get the green circle icon indicating a rotary switch? My version is 1.2.10.32275