Flagrum

The slash in the path name of the Controls Indicator is wrong: device_init.lua creators[devices.CONTROLS] = {"AJS37::avControlsIndicator", LockOn_Options.script_path.."ControlsIndicator\Indicator\ControlsIndicator.lua", {}} dcs.log 2018-04-27 19:03:47.173 ERROR COCKPITBASE: ccLuaLoader::LuaDofile(L, "./Mods/aircraft/AJS37/Cockpit/scripts/ControlsIndicatorIndicatorControlsIndicator.lua"): Missed file ./Mods/aircraft/AJS37/Cockpit/scripts/ControlsIndicatorIndicatorControlsIndicator.lua

Somehow Caucasus 2.5.1 seems to bit quite unstable for me. No matter which aircraft, I get fairly often various crashes - be it when starting a new mission in the ME and clicking on the load out icon (Spitfire) or when flying over Caucasus (Viggen, Harrier). No mods ofc, and in the end, I deleted terrain/Caucaus and run another repair. This crash now happened after starting a fresh mission in the ME with only the Harrier in it. Starting the mission, the load screen appeared and after some time, probably right in the moment when the "fly!" dialog should appear (but still at the load screen), DCS crashed again. See attached logs. dcs.log-20180427-023933.zip

Gunship, C64 :pilotfly:

https://forums.eagle.ru/showpost.php?p=3462801&postcount=114

? ... because they like to work in a structured way and try to avoid chaos by not opening 5 new tasks for every finished task every time someone asks for it?

It was this way during the very first few weeks after the module was released. At that time the flex sight was not implemented yet, and as a workaround a simple reticle projected on the wind shield was provided instead.

Yes. https://forums.eagle.ru/showpost.php?p=3285514&postcount=13

Carrier Air Wing 8 having fun on a field trip today? :D

3D Editor was requested years ago, but also the smaller brother of it, the Unit-Outline-Editor was suggested already several times. So ... +213 for all the previous requests and +1 from me! :D

On which maps are you guys flying? My experience is, that Normandy lags A LOT. Seems to be related to loading data while getting to new areas of the map. It takes about 5-10 Minutes in the same area (i.e. flying in circles) until everything is seemingly loaded and stutters get less and less. Might be ok...ish for helos, but fast movers over Normandy is a no-go for me, at least at the moment. On the other hand, New Georgia is working pretty decent, performance wise. A stutter here and there, but manageble. And then Nevada ... is a real gem. A few fps less over Vegas, but no real st...st...s...t...UTTE...rs.

This is bothering me for quite some time now: the Guides & Tutorials forum is more used to ask all kinds of random questions that rather belong to the module specific subforums, the general DCS forum or perhaps even in the chit chat forum. They are not even questions concerning something in a guide or tutorial that was posted there. Or at least requests for new guides or tutorials. If we allow this to continue, the purpose of that forum becomes totally void as nobody will be able to find relevant threads (i.e. containing guides and tutorials) there anymore. So, if some kind moderator with some spare time would find the time to clean up there a bit, it would be highly appreciated. thanks!

Afaik usual sizes are 120GB, 250GB, 500GB. So that leaves not much choice in your case, right? Also considering that the most space is used for maps and 100 GB is worth 3 - 4 (taking the DCS base install into account) maps today, a 250 GB SSD should last for another 4-5 maps easily. That should cover the next 5-10 years of development time, if you ask me. :-) On the other hand, more space is never a bad idea. It is not like it is wasted. You can always use additional space for other stuff.

see also here: https://forums.eagle.ru/showthread.php?t=196099 & https://forums.eagle.ru/showthread.php?t=202962

Why would you want to do that? Communication is one, maybe the most important function of a RIO. That's like, I put a Lantirn POD on my plane, but for sanity sake, turn off all video feeds.

https://getyarn.io/yarn-clip/a85ab2e4-0d44-4589-a933-8d3be74e5d3a#rJDo8Ws0cf.copy

I read your posting now 3 times ... but could not hear anything!

:huh::doh: (Well, if you prefer a "real editor" instead of what ED offers, then you still edit the generated .lua code inside of a .miz file with your favourite text editor .......)

OMFG ... :doh::doh::doh::doh::doh::doh::doh::doh::doh:

Problem solved. Seems that some files of the Nevada map got corrupted somehow and the DCS repair did not notice this. After deleting the mods\nevada folder, DCS repair did it's job and now Nevada is working again in the mission editor.

Updated to 2.5.0u5 today. Start DCS, enter mission editor, click New Mission, select Nevada map at the coalition screen. DCS logo appears and after some seconds DCS crashes. Did then a DCS clean, DCS repair and tried it again - crashed again. Then I tried the same procedure but with Caucasus: that map loads fine in mission editor. Then, while Caucausus map was still shown in mission editor, I selected File->New and selected Nevada again. Result: crash. Logs show the initial attempt (start DCS after fresh DCS clean + DCS repair and tried to start a mission at Nevada). dcs.log-20180321-224841.zip

:mad: Pat, could you elaborate a bit please where the difficulties are? My understanding - which might be wrong, ofc - is, that the Gazelle should not act any different if either FFB is enabled or no FFB is used. FFB should be "just" an other output(!!) device like any other. The input side is the actual stick position - how the stick position was archieved (manual input or by FFB motors) should not matter at all. Calculating which FFB forces are to be set and timing when they are to be set should be all that comes on top of the default, non-FFB Gazelle. I am not saying that it is easy, but honestly I don't really get how this can be so complicated that you just drop such an important feature. :(

Regarding the logs, you have successfully updated your DCS: STATUS: Successfully updated to 'openbeta' 2.5.0.15365.345

I am not sure if this issue just came up with the latest update - it just happend that I noticed it only now as the SA342 is usually grounded for the time beeing. For the requested info: please refrer to the previous postings. But if time permits, I will experiment a bit more with FFB turned on and off and trying a different (non-ffb) stick.

Watch it starting at 3:15. When deflecting the cyclic right, the helo reactis immediately. But when he deflects the stick then far left, it takes some moments until the attitude changes. In the case of min. 3:15, it takes several seconds. That does indeed look odd, imo.