KirkaFordis Rex

Hey I'm Kirk, DCS veteran and aircraft enthusiast. I've done quite a bit of voice over and acting for some StingTV content. I've done some professional voiceover work, but it's not my main job. I'm a middle aged white guy from the west coast, so I have a very clean American accent. It's great for wingman, backseaters, JTAC and any other American role. I Also have a Gentex helmet and oxygen mask with microphone for realistic pilot vocal tone and quality or a SM300 for crisp studio audio. My normal style: Professional American Authoritative I can also do many accents: British Irish Scottish French German Russian If you're looking to elevate your campaign missions, put together some life like interchanges, or polish a training video I'd love to help out. Shoot me a message on here, or the DCS Discord server. KirkaFordisRex#0377 I'm passionate about our DCS community, and I love seeing quality content get out there to entice the new kids to join , as well as encourage the veteran frequent fliers with some good ole' fashioned jargon. fox 3.mp3 8 Back on you.mp3

I'm in serious need of a DCS sticker for my water bottle. If yall could get right on that, that'd be super appreciated. love you guys, Kirk #showsomeDCSlove

I've just started using MOOSE, I spent a whole day watching the videos, and a second day playing with the example missions. I have so..many.. questions... I'll keep it simple for the first one. I'm spawning units from MOOSE, and I notice that their unit names are just numbers like "1002028" and "1002026" how do I get this unit name and manipulate the unit? I've tried adding the ":InitKeepUnitNames()" to no avail, even the example mission doesn't seem to keep the unit names. Just for testing I tried calling the unit name and putting it in a message to and it really didn't like that. I had to convert it to a string, and I get "table: 0000000718149FAO" local VariableUnit = UNIT:FindByName("Unit #1") trigger.action.outText( tostring(VariableUnit), 1) I'm using the SPA 320 and the SPA 021 mission .luas and .miz for examples.

Just saw the newsletter today, but I also see signups are closed. Is it too late to enter a squadron?

I'd love to hear from Matt about the upcoming carrier module. Or anybody at ED about the plans for DCS in the next 6-12 months.

Have you tried using the F11 airfield view? You can manipulate the view and have the runway insight. Also perhaps put an AI aircraft on the parking area near the center, F2 that aircraft, and then use F5 "Nearest Aircraft view" to see your aircraft in relation to the AI aircraft. Use the Keypad / and * to control zoom. (just a thought)

JAR's about as American as Apple pie. The fact that he was born in Australia grew up in Australia and lives in Australia is irrelevant. :beer: Good luck with the new squad guys. I would definitely recommend the mod for pre-module training. Obviously the carrier is a must, it's fantastic for practicing NATOPS approaches and for getting yelled at by the Air Boss :director:. (If you're into that sort of thing).

Since this is now no longer a beta issue, has anyone created a help ticket?

+1 Can reproduce. I am also having this issue.

It works for me. I have 4 monitors arranged in an upside down "T" configuration. 3 monitors for left, center, right. 1 for MultiFunctionDisplay (MFD) at the top. I have the resolution setup as 4 monitors in a row so that as my mouse moves off the right of the right screen it appears on the top monitor. I have an Nvidia graphics card so I configured the 3 monitors to act as 1 monitor using Nvidia Surround. I also included bezel correction. I was having difficulty seeing the mission editor buttons in 1.5 and 2.0 because they were drawn off screen. I used klem's lua fix and it worked. I'll attach my .lua so you can see what I did. One difference is that I use a local variable called "mybezelscreen" so that if I need to change my resolution, I can just change that one variable and the .lua will still work properly. Hope that helps anybody still having this issue.

Just to add to this. I am also experiencing this issue. Thank you OP for reporting. I Have 4 monitors, running Nvidia surround on 3 of the 1920x1080 monitors. With bezel correction I get a resolution of about ~ 6000 x 1080. My other monitor is 1280 x 960 and display's RMFD My map view is also skewed in the center monitor exactly as depicted above. Additionally I can't see any of the mission editor buttons because they are behind my bezels. (probably a problem for a different thread) Once again thank you for reporting, and thanks devs for a wonderful product and thanks for trying to make it better. -Kirk

You can see this in action with the A10A as well. But it's not a bug on the A-10A The MFD will be exported correctly using a maverick. if you cycle away from the maverick the screen will tint red and eventually white out. If you switch back to a maverick, the screen will update properly again. Hope that helps.

Confirmed this will 'fix' the issue. Navigate to User/Saved Games/DCS.openbeta/Config and delete the options.lua When you restart DCS it will reset the defaults. I had this issue as well. I switched resolution and it set the aspect ratio to 1.something. It would be nice to always have access to the Options menu, even if you mess up like this.

This is a rather confusing thread. I came here to see if 2.0 was still on track to be released this year. Now I'm not sure what to think. I can say confidently that Sith is rockstar for posting so much in this thread and keeping things on track. It's very much appreciated.

Great job all, Those sam sites really keeps a pilots head on a swivel. All while scribbling on a map, writing down the 9-line brief, and checking in with JTAC. It was intense, but worth it.

I figured out a work around. It's definitely not as fancy as peterp's but it works. http://forums.eagle.ru/showthread.php?p=2058697

in DCS World\Mods\aircrafts\Uh-1H\Cockpit\Scripts\CARGO_CAM_base_page.lua line # 11 HUD_OnlyVerts = {{-width,height},{width,height},{width,-height},{-width,-height}} the "width" value is it's position on the screen. By defualt line #7 local width = 1.0. swapping out the word "width" with "1" will yield the same position. The lower this number is, the farther from the right hand side of the screen. Also we can see that the box defaults from -1 to 1 so it is 2 units wide. My resolution is 6060*1080 and this is what I changed my line #11 to: HUD_OnlyVerts = {{-10,height},{-8,height},{-8,-height},{-10,-height}} You can tweak the numbers to get it just right. I'm sure there are probably other (better) ways to do it, but this worked for me. Hope it helps.

Was there an answer to this? Mines in the upper right corner of my right monitor which is located over the right door window. I'd like to move it more into my field of view. running 3 monitors, 6040*1080 edit: I'm currently digging around in DCS World\Mods\aircrafts\Uh-1H\Cockpit\Scripts\CARGO_CAM_base_page.lua

I absolutely love the TARGET software. No you don't need it to fly. And that lag shouldn't be there. TARGET Pros: -Buttons can have multiple features -On button can be programmed to do many things in a row -You can adjust the lighting features on the Throttle in game to show gear down, flare or flaps TARGET Cons: -you have to create/program the script -it has to run in the background -complex scripts might not be compatible between modules, causing you start and stop scripts depending on the aircraft you want to fly for that mission. Like I said, I love it. But I know guys that think it's garbage. To each their own, but it makes my life so much easier if all I have to do is push 1 button and it switches to Air to Air BVR mode, selects a 120C, turns on my radar, sets the range scale to 25km, and the expected target distance to 25km. All in the blink of an eye.

Yeah that's way above me. I just fly with the TARGET software. Why don't you want to use TARGET? Is it because you've spent so much time on this other method?

If you don't run the TARGET scripts and just plug and play the HOTAS your computer will see the devices separated. If you create and run a TARGET script, it combines the HOTAS into 1 virtual joystick with a different name. To set up multiple key strokes in TARGET is pretty straight forward. -Select the button you want and map a key to it. -Add it to the list on the right (assuming you're using the GUI) -map another key stroke and add it -continue ad nausem I don't understand what you mean by "selecting a modifier" however, if you're in the GUI and select an "Advanced" setup when creating a new file you can choose "Layer Options" The layer function is used when you want to have 1 button do 3 different things depending on the layer. As an example make the Boat Switch Fwd the "Down" layer, the Boat Switch Middle the "Middle" layer, and the Boat Switch Aft the "Up" layer. Using these layers we can select any botton on the joystick and make it do 3 different things. Lets choose the Trigger (for simplicity) we can map it to Bring the gear up/down, fire the cannon, or contact the tower and request a landing. Trigger Press -[D] "g" -[M] "c" -[M] "spacebar" - "\" - "F1" - "F1" So now if our Boat switch is forward (selecting the "Down" layer 'D') and we press the trigger, it activates the keystroke "g" If the boat switch is aft (selecting the "Up" layer 'U') and we press the trigger the key stoke "backslash" will be pressed (bringing up the communications menu) then the "F1" key will be pressed contacting the nearest tower, then the "F1" key will be pressed again requesting inbound (All with 1 button press) Similarly, you can create a "Shift" layer that is either "Out" [O] or "In" that works like a layer. The button can do something entirely different if you are holding "in" the shift layer. (commonly the pinkie paddle)

This was indeed the issue. Anything 10 seconds or less would not stay on the screen long enough to see. Thank you gentlemen for your timely responses. -Kirk

I don't quite understand what you mean. I understand that it might work to send the message to the coalition using the code below, but I'm unsure how to use it. I'm still looking for a good example. If I wanted to send this to Blue coalition, what would that look like? function trigger.action.outTextForCoalition(enum coalition.side coalition, string text, Time delay) ^^ This may be the issue. The trigger fires ONCE on MISSION START. Should I put a delay on it? And how much do you think? Type( trigger.misc.getUserFlag ( '1' ) ) -> string it's already a string, do you think converting it would make a difference? I'm not sure how finicky DCS is. I suppose that's possible. And a good work around for sure. I will do that if I can't figure this out. I'd prefer to know why it's behaving the way it is, to debug further scripting errors in the future. Thanks for your posts guys.

Afternoon folks, I had a quick little question. I'm using a script (default lua script not MIST or slmod) in a mission that sends a message, that reads the value of a flag. trigger.action.outText( trigger.misc.getUserFlag ( '1' ), 5 ) This should display the numeric value of Flag 1 on the screen with a message box. It works beautifully, but only in single player. I hosted a multiplayer mission with some friends and the flag was still functioning (best i could tell) but no message to any player. Nor did I specify a player to send it to. I went back to single player and it works perfectly, just as before. What could be causing this? Is there a script that would work better? I've searched the forums and I can't seem to find anything pertaining to scripting messages and multiplayer. Likely due to either my incompetence with the search function, or I am just missing something that is just too obvious Suggestions? Questions? Links? Thanks

It might be nothing... but every now and again I loose the ability to move my mouse around while I'm entering into the multiplayer server list. Alt + Tab will take me out of DCS back to the dashboard, then I Alt + Tab back into it and it works. It might be worth a shot.