Habu_69

Got it working. Tx to all.

Using Reverb Pro, not Oculus. Thinking issue is driver/software related as both devices exhibit same behavior. I have tons of experience with these devices, but this has me stumped. May try unplugging all other USB devices to see what happens.

Is it possible to program a Cougar stick DX button as the SHIFT button in DCS Controls? I wish to set the Cougar S3 to activate the SHIFTED layer. Tried setting S3 as a "modifier" button in controls, but that does not work. I know how to do it with Foxy, but wish to avoid using Foxy, as my old HOTAS will not accept a Foxy upload any more.

I have 2 vintage TM Cougar joysticks (main and spare) I have been using now for about 20 years, using Foxy to program custom key outputs. Using Win 10 1809. As of May 25 Foxy will no longer upload the .tmj files to either device. Upload app just times out. Uninstalled and reinstalled both all the Cougar files and Foxy, but no joy. Really has me stumped! Any suggestions? I suppose I could convert to using the TARGET software, but prefer not to do that. Seems to be some sort of software issue.

Hmmmmm. Wonder if issue could be vid driver? Will investigate. Currently using 441.20

ssd. Need to test with other missions, I guess. Try to isolate the issue. Error appears to be access violation, which usually refers to memory issue, but this is 15 min. into bare bones mission: EDCORE: # C0000005 ACCESS_VIOLATION at 5D97DBF6 00:00000000

Crash While Dogfighting Since about Feb. DCS crashes (video freeze) while dogfighting in both 2.5.5 OB and 2.5.6 OB. In simple 2-ship BFM practice mission (Caucasus) I can chase a MiG all day until he goes vertical. As I pull up losing the horizon in lag pursuit, the video freezes and I get the dreaded DCS purple Waiting box. Anyone else with Reverb Pro experience this? System: Win 10 1809, I5-8600, NVidia RTX 2070 Super, 32 GB DDR4, 800W PSU

Tried simple replacement of Stennis with Supercarrier in older mission in ME and could not get Shooter to recognize keybind to command launch. So I was stuck on the cat. Felt sorry for the unfortunate deck hand standing there twirling his finger forever. Probably thinking "When is this dumb sum'bitch gonna be ready?" Anyone else had success doing this?

1. Need more info to help you, like .miz file, .lua file, etc. 2. You will get much more responsive MOOSE help at MOOSE Discord. https://discord.gg/v9RjWq

BZ on OB 2.5.6.49314 I have voice my criticism of ED's slow and buggy updates in the past. I am here to say BZ on the OB 2.5.6.49314 patch. Is it perfect? Of course not. The program is an early access open beta. This patch, though, fixed a lot bugs, added some aircraft features and added the Super Carrier, all without major game breakers. The patch quality reflects the few weeks additional delay for testing and correcting.

So 1.1.4 changes only the Moose.lua, and not the doc methods, example mission script, etc??

One way is to open the mission.miz file in a zip utility and directly copy the folder containing the sound files into the mission file. Then, if necessary, re-zip the files. Be sure to rename the file to xxxxxxx.miz. The mission MOOSE script will have a line specifying the name of the sound files folder. AIRBOSS example: AirbossStennis:SetSoundfilesFolder( "Airboss Soundfiles Loud/" )

One solution is to place the static at a remote map location and use scripting, like MOOSE, to spawn a copy of the static when/where you want it. So many things possible/easier with scripting. Other solutions may exist. Example MOOSE code: ZonePosition = ZONE:New( "Creech" ) -- Initialize zone "Creech" created in ME SpawnPlane = SPAWNSTATIC:NewFromStatic( "C17_Disabled", country.id.USA ) -- Define object from ME group C17_Disabled SpawnPlaneVec2 = ZonePosition:GetPointVec2() -- Returns (Vec2) position of zone center PlanePos = SpawnPlaneVec2:Translate( 250, 272 ) -- This optional will offset the spawn location from zone center by 250m bearing 272D C17 = SpawnPlane:SpawnFromPointVec2( PlanePos, 70 )

USN would be extremely reluctant to deploy a carrier task force to a place like Black Sea where a few mines or other obstacles could remove it from action elsewhere. The Med is the exception that proves the rule.

Give the attack group the primary task of "Ground Attack" and an advanced WP task "Bombing" and set the target triangle and other parameters. You can't give different targets/actions to different units in a group.

The Moose.lua version you should use is this one https://github.com/FlightControl-Master/MOOSE_INCLUDE/tree/develop/Moose_Include_Static Moose issues will get quicker attention if you address them to the Moose discord.

System: Win 10 v1907; I5 8600K; 32 GB DDR4; NVidia RTX 2070 Super 8GB; 441.87 Vid driver. HP Reverb VR headset. DCS 2.5.6.47224 OB. Simple BFM practice mission Caucasus map with MiG, F/A-18C, AWACS saved in 2.5.6.47224. In VR F/A-18 pursues MiG at rear aspect for gun firing solution with radar gunsight. DCS crashes as soon as SHOOT cue appears. Behavior repeatable and occurred in 2.5.6 prior to 47224 patch, but did not occur with 2.5.5. No .trk file due to crash. Log attached. More testing. SHOOT cue was coincidence. DCS crashes when F/A-18 gets close (> 1NM) to the MiG. dcs.log-20200418-135733.zip

Interesting concept and I think the objective can be achieved with scripting, but I don't have time to look into it now.

A new Moose thread is a good suggestion IMO. Re LDT, I began trying to learn Moose scripting with ZERO coding experience and now consider myself a mid-level Moose script user, certainly not a developer. LDT was bit of a pain to install correctly, but I agree with Hardcard that the effort and frustration was worth it in the end. Opposite views are certainly valid. My experience in the Moose "community" has been nothing but positive. Pikey, Frank, Hardcard and the other Moose experts who have stepped in, not only to keep Moose relevant, but to build and expand its capabilities merit high praise. All anyone has to do is politely request assistance on the Discord channel and someone jumps in to help, usually within a few minutes. A toast to FC. We miss him and wish him well.

One other time saver you may be unaware of is to do mission/script testing with the DCS ME in window mode. This allows for very efficient script editing and testing.

The Load Script File trigger for your script must be updated at every instance of changing the script. The mission file does not update automatically. Alternatively you can use this device in a Load Script trigger action for testing: dofile([[Full_Path_To_Your_Script.lua]]) -- for example: dofile([[e:\Game Data\Scripts\Mission Scripts\Air Boss.lua]]) This will reload the script each time you run a mission. Be aware that this is the script path on your PC, which will not work for anyone else, so on completion of testing replace the dofile with the normal Load Script File trigger action.

1. Not sure what you mean by "versions". When DCS spawns a late-activated unit it adds a post-script identifier to the unit names, like "Spawn Vehicle 1 001", or something like that. To overcome problems with changing names you can use the Moose spawn method SPAWN.InitKeepUnitNames() or other methods described in the docs. The most recent version of Moose can be found in the develop branch link that I referenced. 2. If you installed Moose to work with LDT, then over-write all the files and folders with the updated ones from the Github develop branch. But then for LDT intellisense to work properly you have to do the following: 1. In LDT, Rt.click Moose_Framework 2. L click: Build Path/Configure Build Path 3. Select Source Tab 4. Select Add Folder 5. Select in box: Moose_Framework/../ 6. Click OK 6. Select APPLY AND CLOSE 7. Observe LDT refreshing workspace.

You are using the wrong file to load Moose. Download the group of files from here: https://github.com/FlightControl-Master/MOOSE_INCLUDE/tree/develop then load the Moose.lua from the Moose_Include_Static folder. It is about 5 mb.

I think 78383669 is the id of the zone, not the scenery object.

You should be able to discover the freq by using the ME and selecting the group.