Snacko

I found this a while back, and cannot find any good info on how it works. Here is what I have figured out so far: If you right-click when you are in the F4 or RCtrl+F2 view you get a Camera/Clipboard menu across the top of your screen. It has 3 buttons: Predefined Bookmarks User Bookmarks Clipboard For me the DCS Predefined Bookmarks menu is empty. But I can see a line at the bottom, which is cutoff, so I wonder if it's just not displaying correctly. The User Defined Bookmarks has 2 items: Editor Visible These don't seem to do anything. The last button lets you Copy to Clipboard. I pasted this into notepad and it had this just had text defining the coordinates and angle of the camera. But I don't know what to do with that. However, I have found that if I save the view to the Clipboard and press F12, and it will zoom out and up from that view about 50 feet, and then drop you into the cockpit... After doing this a few times I noticed a wire-frame of the 'default' camera in the view. This looks like the Default position of the RCtrl+F2 camera. It would be awesome if we could predefine(bookmark) views that we could use over and over anytime for any aircraft. Does anybody know how this works??

... Is this considered a bug/issue? Or is this by design? The lack of any response has now got me wondering...

Like the title says... I've had this monitor layout for many years. I go all the way back to Lock-On.. It has always been this way for so long... There may be a few other views that also do this. Can we just get this fixed? Thanks.

This Bug still persists, and is very annoying.. In the Triggers you can set the smoke density from 0 to 1. (ie. 0.1, 0.2, 0.3). But you Still cannot set the Smoke Density like this in the Mission Editor Static Effect properties panel. I wish ED would spend a little time fixing this kind of 'low hanging fruit'. You know it will be very easy to fix. It's just changing it from an Integer to a floating point number. Heck, it's probably just a setting some control's property.. And while you are at it, please add a Z axis to the Effects, so we can change their height. Just want to add smoke to some factories & Oil Platforms and processing.. As it is, it just looks like they are on fire..

Oh Man! Thanks for that!!

I've tried this several times, and I get stuck on the catapult.. After the deck crew signals to Retract the Launch Bar, they walk over to the side and some signal where his left hand is behind his back, and his left hand/light is moving across his chest to the right, and back again, over and over.. After retracting the Launch Bar, I expected him to tell me to throttle up... But I don't know what he wants me to do??

That would be great. To make sure I understand this file... It would be a rotor whirl sound when the collective is pulled up or down causing significant Gs? Or just a transition sound between the low and High sounds? Or maybe I'm saying the same thing twice? LoL

What do you mean by that? No shaking happens from DCS only via testing through sound module. He was replying to my question about a specific sound file not being found.. (But I wonder if I just created my own sound file with those names. Hmmm...)

Have you checked your Export.lua file? If it works but not in DCS then that might be the problem.

If you mean the sound files to shake. They are in your Documents folder under Simshaker/base

The Sound module has been locking up on me in different aircraft the past few weeks. Today I was flying the apache, and saw these missing files. But other aircraft did not have missing files. It seems I'm missing files for the Apache? I everything under the 'base' folder and these are not there... h_2_0_1_LS not found h_2_0_1_RS not found h_2_0_1_LB not found h_2_0_1_RB not found

Thanks for the replys... Good info.. I finally noticed that if I just press TX1/2 again, the menu goes away..

PS: Now that it's working I have another question.. When I say a command and it gets recognized, the Comms menu stays open afterwards. I have to manually close it with F12, to get other F1, 2, 3.. view keys to work.. I don't want to disable the Comms menu. Just not have it open when I 'say' a command. Only open when I press the \ key.

No worries! Since I've got it working and noticed the 'Advanced Command' option, I realized that somehow most of the switches in VAICOM had been turned off somehow. I hadn't used it in several months, and I remember I had it all setup like I wanted. But I didn't see how it could make any difference for such simple commands. I could have just turned that on before I reinstalled, and the old install would have probably worked..

I was going to post this earlier today, but then decided to just backup my VA files folder and start fresh. It seems to be working now. And I noticed that when I said request takeoff, the log said something about Advanced Commands being disabled.. So, I turned that on, and it's working now. I don't know why Request Takeoff needed Advanced Commands on?? Maybe I'm missing something? Anyhow, it's fixed I think. Thanks for your help on this sthompson! null

Yes sir.. I was wondering if it had something to do with MT vs ST.. I was testing in MT all of the time. But then I tested in ST and it seemed different. Hard to tell without intense focus.. I'm 65, and don't have it like I used to..

Thanks for that info.. I did the Test and it says my profile matches. But I went ahead and clicked the Finish button to copy the keywords anyway. When I went into my profile to update the keywords, the current keywords went from AAA, ...... Zaqazig. When I pasted my clipboard in, it only went from pasted this: *Bomb*; *Bullet*; *Dart*; *from the East*; *from the North*; *from the NorthEast*; *from the NorthWest*; *from the South*; *from the SouthEast*; *from the SouthWest*; *from the West*; *GBU*; *Guided*; *Gun*; *Marker*; *Maverick*; *Missile*; *Paint*; *Paveway*; *Pickle*; *Rocket*; *Smoke*; *Stores*; *Strafe* Also, with Debugging on. At startup I only saw one error: 5:01:08.227 Object reference not set to an instance of an object./n at VAICOM.Database.Aliases.BuildKneeboardAliasList() Arggg... What's going on!?..

Thanks for the reply Frappie! I forgot to mention which controllers the conflicts were on. I didn't include that in my original screenshot. But it was either the WW Combat panel or the Take-Off 2 panel. So, when you look for the conflicting bind, you have to look at the correct control for the aircraft in contention. So, let's start over.. Here I try to assign the JOY_BTN37 on the Combat Panel, and it shows Gear binds on about 20 other aircraft (but you can only see 3 in the screenshot. I couldn't get a screenshot, or copy of all of the ac. DCS erased it when I pressed ctrl+c, the tooltip disappeared when I took screenshots.) And the bind is not in the Combat Panel's diff.lua files for these aircraft, so there's no code to show you.. I did a DCS Repair on 'ALL Files'. It took about 20 minutes. Still no Joy.. It strange that the Same button number is on the Takeoff Panel.. There's got to be something to do with that. But here are the two filenames in the Mig21 joystick folder: WINWING F18 COMBAT READY PANEL {3C2398C0-75AA-11ee-8010-444553540000}.diff.lua WINWING F18 TAKEOFF PANEL 2 {3C232390-75AA-11ee-800E-444553540000}.diff.lua

I reinstalled VA and Vaicom, and did a full repair of 'All' files in DCS .. No Joy!!

Thanks, it's attached. It includes the .jp files that JoyPro creates. I moved them to another folder after zipping and tested again. It didn't make any difference. It only happens in the UI Layer.. And each time I restart the game it has different conflicts for the same buttons that I have tested. Really weird.. I'm going to do a repair and see what happens. Input.7z

Yes, I have a short pause between commands. 'Tower' and 'Request Taxi to runway', 'Request Takeoff', etc., are all recognized with 94% confidence. I have my radio set to the correct freq for the tower. And I tried TX1 & TX2.... I think I'll do a reinstall and see what happens..

I've checked several of these 'Currently in Use' conflicts in the UI Layer, by checking each individual aircraft. None of them are real. There are no conflicts with other binds to the same control. (And I am not talking about the Red x warnings in some controls.) I've recently used JoyPro to assign all of my binds, and it's an amazing tool, and worked wonderfully. I have validate all of my binds, and there are no conflicts. And this only happens in the UI Layer. Does anyone know how to fix this? In the UI Layer, when you assign a bind, it loads all of the other aircrafts binds to check for conflicts. But it's reading something wrong.

Just getting back into Vaicom.. I have Easy Comms off. When I say 'tower request takeoff', Vaicom says it recognized the command every time with high confidence. But then it says (awaiting additional input) How can I fix this??

Sorry, I missed it. Who said it will be released at 1500 gmt?

Before all you rocket jocks start posting "Don't use easy mode, it's for girls", or "If you want an 'easy' mode, you've come to the wrong place!". I'm just wanting to understand it's current state. DCS did used to have an Easy mode, but I have not looked for it for years.. But I have a friend coming over next month, and I was wondering if it still works? How does it work? I've read that it's bugged, but I want to look for myself. I have the Mig-19p and it has an 'easy' mode(MIG-19P_easy) aircraft in the Controls Settings, and I've assigned the basics to it. But when I go to the Mission Builder, or "Create Fast Mission", it's not there for selection. And I've see other 'easy' aircraft listed in the install files(F-86_easy; FW-190A_easy; FW-190D9_easy; KA-50_easy; P-47_easy; and several more.) that are also not available in the game. So, is this 'Easy' mode just simply completely abandoned in DCS. And the BF-190K-4_easy that is in the Control Settings just a mistaken left-over that should be remove? Or is Easy mode still functional in any way at all? Thanks.