Teej

Could be. I've got a couple more multiplayer flights I can check...I thought I experienced the same on a previous one, but I'm not sure. In the meantime, to clarify, this was on: 1.5 Stable Rift CV1 OH 1.4 GTX-980Ti

Is this known? Didn't see anything in Skate's known bugs list post. Flew in multiplayer with several other non-Rift users including the server. I went back today to look at the track (flown Wed. night). Unplugged the Rift, closed OH, launched DCS and tried to replay (full screen, non rift mode). At spawn, the camera isn't in the right place. That's not a big surprise as it's always somewhere out of / above the jet when I start, and I have to Num-5 to get into the seat. However, that doesn't seem to work on the replay....I can't view from within my jet. Did a LCtrl-F11 to watch the flight from the outside. Try to padlock on my jet and the jet is not centered. When I try to zoom in, it seems to zoom on the wrong spot, throwing my jet out of the frame. Track plays, but none of the views are right. Even trying to pan around with the mouse on the ground doesn't help. I got a copy of the flight from a non-rift user and it plays perfectly.

Just as a data point...I checked and I'm running OH 1.4...on a GTX 980Ti....I am not clock-locked - EVGA tool shows card running at full speed.

Flew tonight with the framerate up. When I remembered to look, it spent a fair bit of time at 45, usually when other jets were filling my view. There was a lot of times it was showing 90+ though. I haven't yet looked to see if I've got the "slow GPU speed" OR bug.

Essentially same specs as you except I'm on rift. Haven't gone on a busy server but I've been flying formation with 5 other jets at mustard-pass distance, and it's smooth to me. I do have horrible stutters turning my head in the menu screen but in the 3D world it's great.

No going back for me. Need /want kneeboard info but other than that...

Lawndart usually makes our videos. I've not had time to try any other planes yet and I'm afraid I won't be gaming much for a few days. I'm sure someone else who has will chime in!

Sharing my perspective from initial impressions with the rift... tl;dr - loving it so far. After a couple of test flights and fiddling with graphic settings (mostly for naught, apparently - resolution at least is hard-coded for DCS / Rift) I jumped in with the team to fly our “high show” demo. Worst things first - I’m looking forward to better resolution / clarity someday. Looking around my cockpit, I can see where the needles are and such but reading details takes some effort / leaning in. Fortunately the Rift and DCS handle that quite well. I currently have the Rift’s sensor/camera positioned to the right of my flight seat, rather than in front of me. I can actually lean over, across the canopy rail and look down and read “Opposing Solo” painted on the left side of my jet. TrackIR never worked that well due to using a total of 3 reference points to determine both position and orientation. Rift on the other hand uses the camera for position only - orientation is sensed by gyros on the Rift itself. We taxied out and did “lightning takeoffs” (each jet sequentially rather than the 4-1-and-1 launch) and formed up in delta afterwards. Doing this without the rift, I usually used padlock to help pick out the jets in the distance as we merged into Delta, however padlock is not available with the rift. And that’s about the end of the negatives as far as I’m concerned. Can you wear it with glasses? I can; I was doing so on this flight. The rift’s field of view was larger than my glasses. It’s about like putting my nose 6 or so inches from a 24 inch monitor. Comfort was not a problem. As I approached the formation, I was treated to the spectacle of 5 F-16s in glorious 3D. The sightseeing was shortlived - before long…..’Blue out ready now!” and Panther and I departed the diamond, heading out behind the show line. Moments later “….let’s hack now!”. Here we go. One of my biggest concerns with the Rift was spotting 5 from ~ 3 miles away down the show line in order to line up the ‘hit’. “….8,000 SMOKE!” Ahhh, there you are. :D Bam. Solid opposing knife edge hit, just a little show right. Essentially the same story on the opposing inverted. Knife edge and 8 point passes are irrelevant regarding the Rift, but set up the next challenge and opportunity for the Rift to shine or shrivel for my purposes. Peeling off from the 8 point, I spin my head around to the left, looking over my shoulder, tracking 5’s smoke trail for the aileron rolls. Take a few glances back forward monitoring my flight parameters. SA with the Rift is nothing short of amazing. Rejoin is almost effortless as we set up for the Calypso. In the past I’ve usually flown Calypso using padlock. Not an option with the Rift and I don’t miss it a bit. This is much better. It doesn’t take long to realize just how messed up your proprioception gets when you’re using padlock or trackIR, having your real eyes facing forwards and your game eyes are looking 90 left…and (using TIR without padlock) your head is turned somewhere in between. We exit the Calypso and line up for the crossover break. Once again, the larger “visually accurate / 1:1” field of view is a big plus. Hard to put into words just how different it feels when you’re not looking at the world through a monitor-sized window 2 feet or so in front of you. Opposing split-S…more awesomeness. Pull up into the climb, making the initial hit/cross…hit target numbers and roll inverted. Coming down through the vertical as 5 makes her line call, I crane my head back and acquire the pointy end of 5’s smoke trail…”6, visual!” Not that spotting 5 was ever that difficult with TrackIR - this is just SO much more natural and intuitive. I know 5 ought to be straight out from the top of my head….that’s where I look and that’s where 5 is. Perfect. I make my turnaround for the high alpha, having entirely too much fun looking around watching 5’s sneak pass, then sightseeing down the line as I look back to watch the high-low hit unfold. Then it’s a tour of the countryside while they fly the 5-card loop….do my VR and MTHC and meet up with 5 en route to catching the diamond for the delta series. Grinning a mile wide as we split up heading for outer wing positions. Oops. Overcook the rejoin and now I’m looking back at my 5:30 position reaching for leverage on a handhold that isn’t there. :D Walk it back in, getting there in time for a loose delta BUP. Spend the rest of the delta series enjoying my view of the formation and adjusting to holding position the way it was meant to be done. Relieved when we get to the delta burst. Come around and follow the diamond in for the High Bomb Burst. Over the top and I aim at the dirt to intercept 5 for the reflection pass and…I’m blind. Despite knowing where 5 should be, I’ve always relied on padlock to pick the jet out among the ground clutter from nearly 3 miles up, usually acquiring tally before she started popping smoke. Now I’m gonna need that smoke… And that’s that. Is it perfect? No. I suspect what I want (the visual quality we can get in a good monitor today) is at least another 5-10 years out. Gonna need several times the GPU throughput and higher spec displays to match. That said, the resolution is adequate (especially since it’s pushing the upper crust of today’s GPUs) and the package as a whole is staggeringly good. I don’t know how much of that credit goes to the ED / DCS team, but I’m sure it’s more than a little - THANK you - this is some awesome work! How far we’ve come from my first flight sim. :D Yeah. I’m old.

I had tried flying with triple screens but could never get comfortable for formation work with it. Used the triples for racing a lot. I've summarized my initial experiences here (I've had it a very short time - only ~ 3 hours of use at the time I wrote this... http://forum.virtualthunderbirds.com/viewtopic.php?p=35802

I got through my team flight... Just under an hour inside the rift. Had a low grade headache pop up in the final 5 minutes but nothing serious. Certain things sometimes throw my equilibrium off for a second but again nothing serious. I'm happy. Sure made the post-flight beer taste good. ;)

Got my Rift today...Just flew a 6-ship high show. VERY cool. :D Do we know what the optimal settings are re resolution, AA etc to get the best image out of this? Tried a bunch of things and it's getting there...but If there's better to be had I'd like to see it. T

Haven't forgot about ya, bud, but yeah I've been a little tied up. Might be able to look at that a bit further next month if I'm lucky. Heh.

Oh good, he got my good side. :D

Yes you could use that as a rudder. It is a self centering axis input.

Do stop in and intro yourself!

Oh for...no, a mod didn't delete my post, I did, and I did get your PM. ;) PMs don't save in your out box here by default.

Actually, I bet I know why it's not working for you. I did it in an SFM jet and you're probably trying to do it in a newer AFM/ASM setup that doesn't support the ...ThrustCommonDelta parameter. Got an idea what needs to be done for AFM/ASMs...lemme try on one of mine and get back to you...Won't be quite a cut-and-paste thing - it'll probably need a small change for every plane you want to use it on.

I meant that I did that just before posting it. Flew around for 5-10 minutes like that. I did that in 2.0 alpha though. Hmmm.

That can still work. The advanced systems just add a step or two. Paste in here the lines from the sabre's keyboard default.lua file that reference the speedbrake commands you want to use as well as cut & paste the list of devices from devices.lua.

Hmmm. I didn't have any trouble. Went into my mouse default.lua, commented out the existing MOUSE Z line and inserted: {combos = {{key = 'MOUSE_Z'}}, action = iCommandPlaneThrustCommonDelta, name = 'Mouse Thrust'}, Then launched the game went to axis settings, clicked on the "Mouse Thrust" Mouse Z entry and chose "axis tune" and turned on invert & slider checkboxes. Worked for me.

That's one of those things I thought I might have goofed.... make it: dispatch_action(nil,431) I've never seen anything but "nil" in the first parameter...and the third parameter is for an axis...like joystick pitch. If it makes you feel better, use (nil,431,0) :D

Let's start here. Keep in mind I'm writing this without direct access to DCS at the moment, so I might have goofed something up. It will show you all the necessary parts, however... OK. Given your programmer background, this will generally be pretty easy to get you through…but recognize it won’t pass an “integrity check” so if you’re attempting to use these to your advantage in a multiplayer scenario, please don’t try :D LUA is a full-on scripting language, and what you’ve seen with the keymapping is only a piece of it. What I’ll show you is how you can have a piece of LUA code called whenever you hit specific commands. At that point, you can either issue additional commands on the back end, or (using typical programming control logic) decide what to do. Let’s say I want to make it so when I hit “LeftAlt-V” my gear and flaps are lowered. The first thing I need to do is go into my mods/aircraft/[mod]/input/[airframe]/keyboard/default.lua file. Somewhere in the middle of the file that makes sense to me…like…near the commands you want to duplicate, add a line like this: {combos = {{key = 'V', reformers = {'LAlt'}}}, down = 7000, name = ‘Gear and Flaps Down’, category = ‘Lucifah’}, What this means is that when you hit “LAlt-V, it will send a command “7000” (As far as I’m currently aware, anything over 4000 should be OK and won’t conflict with DCS any time soon) to DCS. It will show in the keymap settings as “Gear and Flaps Down” and it can also be seen if you click the category at the top and select “Lucifah”. This lets you group whatever custom work you do together… DCS doesn’t know what command 7000 means - and that’s a good thing. We’re going to tell it. You see, DCS doesn’t directly know when you hit a certain keypress, there’s an input processor that converts your key / axis inputs into “command” codes. Most of what you see in the default.lua file is “friendly names” like “iCommandPlaneGearDown”, but they all translate to codes…. gear down is 431, flaps down (landing flaps) is 145. So now let’s go to your aircraft’s cockpit/scripts folder. Among other things there should be 2 files we’re interested in… “devices.lua” and “device_init.lua”. If those don’t exist, that’s not necessarily a big deal. For now let’s assume they do. Open up devices.lua. You should see something like: local count = 0 local function counter() count = count + 1 return count end -------DEVICE ID------- devices = {} devices["ccKneeboard"] = counter() -- 1 We’re going to add another device. Assuming you have the devices=() line, then after the last “devices” line listed, add one more: devices[“MyDevice”] = counter() — 2 (the — makes things a comment, the number is just there for your reference/debugging if it ever becomes necessary) Save the file and open device_init.lua Hopefully you have a section of code that starts similar to: creators = {} creators[devices.ccKneeboard] = {"avKneeboard",LockOn_Options.common_script_path.."KNEEBOARD/device/init.lua"} Let’s add the following in that section… creators[devices.MyDevice] = {“avLuaDevice”,”MyCode.lua”} Put this way, it’s going to look for a .lua called “MyCode” located in your DCS root folder (ie c:\program files\DCS World). Trying not to get too deep with customizing everything all at once… Save that file. Now let’s go to your DCS root folder and create MyCode.lua Let’s make the contents: — <- remember — makes a line a comment — Get handle to device code: local MyCode = GetSelf() — “subscribe” to command 7000 (as defined above in the keyboard default.lua we changed above). — Whenever DCS gets a 7000, it will call this file’s SetCommand function. MyCode:listen_command(7000) — So when we get called, if the command is 7000, we’ll drop the gear and flaps. function SetCommand(command,value) if (7000 == command) then dispatch_action(nil,431) dispatch_action(nil,145) — elseif (7001 == command) then — — do something else — end end end

Well, when you said "no external tools" I read that as "within game only". Lua is an external tool, just one that DCS uses heavily. If you're allowing "juggling luas", that's not terribly difficult...if you want to talk specifics, feel free to post some more details of exactly what you want to do either here in the thread or PM me. Teej Note: The following are both valid scenarios - the specifics are just to put a context around things - that's why I say be very specific about what you want - the details of the answer depend on the details of the question... 1: "I want DCS to drop my flaps any time I drop my gear" 2: "I want a new entry in DCS controls that will do both - drop my flaps and gear, without changing what happens with the normal flaps / gear keys"

Quick question - is there a way to manually set the random seed when running a mission? I know when you save your track after a mission, the seed gets saved in the .TRK file and read back at load time as in: 00123.147 INFO DCS: Dispatcher: initial random seed = 4738027 00123.227 INFO DCS: Dispatcher: reading track, last event at 12.206000 00123.227 INFO DCS: Dispatcher: read seed = 4969925 00123.227 INFO DCS: Dispatcher: read version = 1508170900 00123.227 INFO DCS: Dispatcher: apply random seed = 4969925 Every now and then I've played a mission and I'd like to at least try recreating some of the "randomness"...I know it still won't be exactly the same, but if there's an easy setting / file I can use to force this I'd like to play with it. Thanks! T