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.