

aeliusg
Members-
Posts
260 -
Joined
-
Last visited
Content Type
Profiles
Forums
Events
Everything posted by aeliusg
-
X-55 Rhino Hotas Issues and Problems
aeliusg replied to Raven434th's topic in PC Hardware and Related Software
I don't know about how the X-55 interacts with the newer AMD chipset, but if your build is for DCS I would return the FX-8350 and MB for an i5 4690K setup anyway. -
Sounds excellent, Boris. I was waiting to hear some impressions from someone besides the Battlefield 4 addict when it comes to this monitor. I've always wanted to use LightBoost/ULMB in conjunction with TrackIR, but compatible TN panels have always looked so dull; and then there's the problem of getting a consistent 120 fps with such a CPU-limited engine (like FSX). Anyway, thanks for your thoughts.
-
Try this one: https://www.digitalcombatsimulator.com/en/files/274488/ Also: Lino's Beacon Map https://www.digitalcombatsimulator.com/en/files/588673/
-
Recommend a Great Joystick for DCS?
aeliusg replied to Visceral Raptor's topic in PC Hardware and Related Software
Special thing about the Warthog is that it is all hall sensors. Every axis. Even the slew stick some people find annoying is actually a hall sensor ministick albeit a low resolution one. -
I think people were having issues with the toe brake components on the Saitek Pro Flight Pedals, but the Combat's are a bit better in that regard. I haven't had any problems with them. With the center detent removed, I see no reason to upgrade unless I can put some load cell brakes on them.
-
Recommend a Great Joystick for DCS?
aeliusg replied to Visceral Raptor's topic in PC Hardware and Related Software
Both a Warthog and a T.16000M for ya? Well, why didn't you tell us you were made of money! :D FYI the Warthog and T.16000M both use the same gimbal system (ball in a cup kind of thing, essentially), except the Warthog has a much stronger centering spring. If you get the Warthog you won't need to bother with the T.16000M unless you're one of those Star Citizen die-hards that want to use dual sticks. Also rudder pedals are much better than any sort of twist if you can afford them in addition. -
Mods and Tweaks for VR (Oculus Rift)
aeliusg replied to RoyMi6's topic in PC Hardware and Related Software
Excellent work, Roy. Thanks for these. -
One 780 Ti is plenty for three monitors at the moment, and SLi isn't supported yet. You can get another one when EDGE comes out if you need to maintain 60 fps. Also, Nvidia's new 900 series is supposed to be on sale in as soon as a week. May be worth waiting for.
-
DCS World environmental shaders mod
aeliusg replied to Mustang's topic in Utility/Program Mods for DCS World
Looks excellent, my friend. -
This should work: ["d3020pnilu3020cd9vd-1vpnilvu1"] = { ["added"] = { [1] = { ["key"] = "JOY_BTN28", }, }, ["name"] = "Armament Off/Safe/Armed Down Toggle", }, ["d3020pnilu3020cd9vd1vpnilvu-1"] = { ["added"] = { [1] = { ["key"] = "JOY_BTN27", }, }, ["name"] = "Armament Off/Safe/Armed Up Toggle", }, The commands for the Armament Toggle switch are different yet again. They only increment up and down, but as long as you have your switch in the ALT position when loading into the sim, this should still work. Replace all of your Armament Off/Safe/Armed commands in the diff.lua with only these two, and you shouldn't have any duplicates. BTW, karls' data.lua only adds some extra routines so we can add new commands with the diff.lua. The change from 1.2.9 to 1.2.10 did not affect it, but I expect the EDGE update will break it totally. On the other hand, maybe ED is doing some revamping themselves, and we won't have to modify it next go around. In any case, we'll still be around to help. I will try using TARGET later as it may be a more long-term solution, but it has its own drawbacks with the virtual controller stuff.
-
Make sure you've replaced your previous bindings (Nav Lights Flash/Nav Lights Off/Nav Lights Steady). You should only have Nav Lights Flash Toggle and Nav Lights Steady Toggle. Also, make sure you have the modified data.lua installed: http://forums.eagle.ru/showthread.php?t=124480 (see attachment, this goes in the Scripts\Input\ folder in your DCS install) "nil" is nil in the sense of a "blank". There is simply nothing, like before the big bang. "0" is the particular value which stands for Nav Lights Off when used in conjunction with action 3002, cockpit_device_id 7. The programmers could have chosen "10" for it, or even "-2000". I hope you can get it working tonight. I will try TARGET tomorrow, and if you wish, I can walk you through that as well. 1.2.10 did not break the data.lua mod, but anytime they update that particular file, I suppose it will be broken. EDIT: Nice explanation, Yurgon. Unfortunately, it seems Microsoft does not care. Their recent Xinput protocol is even less functional (for our purposes).
-
Here you go Avio: ["d3002pnilu3002cd7vd1vpnilvu0"] = { ["added"] = { [1] = { ["key"] = "JOY_BTN13", }, }, ["name"] = "Nav Lights Steady Toggle", }, ["d3002pnilu3002cd7vd-1vpnilvu0"] = { ["added"] = { [1] = { ["key"] = "JOY_BTN14", }, }, ["name"] = "Nav Lights Flash Toggle", }, This should work.
-
OK, I see where you're stuck at. In the regular commands there are three states for action 3002, cockpit_device_id 7. This is the long way to say the Nav Lights toggle switch. -1 is Flash, 0 is Off, 1 is Steady. By default these are all separated into three bindable commands. d3002pnilunilcd7vd1vpnilvunil is the Steady command. This only works for a button press or "down" bind. The d3002 part in the beginning means that "down" activates action 3002. p is nil, or no action when the button is held pressed. u is also nil, so no action when the button is not pressed. cd7 is there to narrow it down to the nav lights switch, you don't have to worry about this, but make sure it is cd7 and not anything else. vd1 says that when you press the button down, the value for the action is 1. This turns the lights to steady. vpnil, no value; vunil, no value. Now the Pinky Toggle switch is essentially two buttons and a middle position with no signal, as you know. There's no way to define the middle position, except as a NO press like you said. DCS uses the "up" part of the command for NO press. So you split the three-way toggle into two commands: a normal command, and an down-up (pressed/NO press) command. The normal command can be Pinky Back for Nav Lights Flash. At this point putting the Pinky Switch in the middle again won't turn off a thing. Now bind Pinky Forward to Nav Lights Steady. At this point, moving it back to the middle also won't do a damn thing. Now here's where the lua editing comes in. Take the d3002pnilunilcd7vd1vpnilvunil stuff and change it to d3002pnilu3002cd7vd1vpnilvu0. This gives you the toggle. As long as the Pinky Switch isn't set forward, the command will count it as "up" and send value 0 to action 3002, toggling lights off.
-
DCS World environmental shaders mod
aeliusg replied to Mustang's topic in Utility/Program Mods for DCS World
Your SweetFX settings look great. I think I tried them once. What I was saying about the clouds is that they look quite gray. Look how bright your plane is compared to the clouds. At that altitude the clouds should also be very bright. -
No problem. Are you using TARGET or the diff.lua method? DCS reads a NO key press as an "up". When a button is not pressed, it is "up". The diff.lua edit I posted gives you a two-way toggle between Button 13 (Pinky Forward/Up) and Button 13 "up", that is when Button 13 is not pressed. You then bind Pinky Back/Down to the other nav lights function, and you have your three-way toggle.
-
Put the following under keys in your diff.lua (using Notepad++ or equivalent): ["d3002pnilu3002cd7vd1vpnilvu0"] = { ["added"] = { [1] = { ["key"] = "JOY_BTN13", }, }, ["name"] = "Nav Lights Steady/Off ", }, This is for Pinky Up. Then bind Pinky Down to Nav Lights Flash. What d3002pnilu3002cd7vd1vpnilvu0 means: d means down (a button press), 3002 is the action (look in the regular .lua), p means pressed (holding down the button), u means up (button unpressed), cd means cockpit_device_id (see in regular .lua), vd means value_down (see in .lua, in this case it is 1 because pressing the button - down - turns nav lights to steady, in action 3002), vp means value_pressed, vu means value_up (action 3002 with value 0 returns nav lights to the off state, set value_up to 0 to have it turn off when the button is "up")
-
DCS World environmental shaders mod
aeliusg replied to Mustang's topic in Utility/Program Mods for DCS World
TBH these clouds look awfully dull. The clouds in your previous screenshots looked more like actual clouds. Maybe our monitor settings are different? -
No easy workaround, unless you consider TARGET to be one :lol:. I might whip up a diff.lua for you, but I'm still figuring things out myself. Edit: OK, karls had this figured out: http://forums.eagle.ru/showthread.php?t=124480. But any time DCS is updated it will probably be screwed up, so might want to learn TARGET.
-
With EDGE comes unified UI, so perhaps you'll be able to change those options without logging-out.
-
Buttkicker Gamers pop up on Ebay pretty often. They're usually the original version, though. Aura Pro Bass Shakers are ready to go if you buy an amplifier to drive them, something like this: http://www.parts-express.com/dayton-audio-sa70-70w-subwoofer-plate-amplifier--300-784. Might be worth waiting for the Buttkicker Gamer to come in stock, though. They give you a good package for the money, though some people think the amplifier is a little underpowered.
-
I don't think it's advisable for civilian aircraft to fly in war zones. ATC or not.
-
Canclelled L-39 -> what licence agreement...
aeliusg replied to fjacobsen's topic in How To Mod for DCS World
No need to mention UH-1H or Mi-8. These modules have been delivered, and your money already taken. :P As far as I know, we have no agreement with ED concerning further development of beta modules. :book: And neither the UH-1H nor the Mi-8 are actually in beta anymore. But FWIW, from the September progress update, apparently we can expect multiplayer cockpit in the Huey and Mi-8 in the future. And I remember a Belsimtek dev popping into one of the Huey threads concerning EGT modeling to say that no, it hadn't been forgotten. Mi-8 manual has been promised. It isn't all bad. Besides, for what I paid, I feel like I have gotten a good deal out of both of these modules. More than any boring "AAA" retail game I've ever paid $59.99 for. -
Kuky, how far away are you sitting? Part of the advantage of 4K is that since the pixels are so small, you can sit closer without seeing the screen-door you get with a regular HD screen of that size; then, the extra FOV is appropriately in your peripheral vision. Does wonders for your sense of speed. If you can suspend your disbelief a little, of course, as you're still looking at a flat two-dimensional image.
-
Well considering the low resolution already puts you at a major disadvantage in terms of actually seeing anything, Oculus only servers would be a necessity anyway. Looking over the shoulder isn't that much of a problem, but you'll have to keep up your IRL physical conditioning if you want to have any marathon turning battles. :P Edit: Didn't see your post, as I was writing mine, AurelTristen. I have to agree with you, the sense of actually knowing where you're looking independent of any visual references is immensely satisfying with the Rift.
-
Broken Hotas Warthog Joystick.....
aeliusg replied to AkheirAX's topic in PC Hardware and Related Software
No, not really. You'll have to determine precisely what the broken part is, then have TM send you that. Easier for them to send you a new one, I'd think. Have they given you a response yet?