Gorgok

I saw this posted about in Hoggit and have a tablet around that i almost never use, thought that sounds clever as well. But i am not sure what i am missing, i can't get my H610PRO to assign. I have the custom driver installed, I see PenTablet in USB (details say driver provider VRK version 1.0.3.7) but it just doesn't do anything... do i need WinTab? Or some checkbox i missed in VRK to make it see the thing? Or it just won't work with this tablet (it is kinda big too...)?

It was the 1.1 version, and the same download even between me and friends (shared over local network). Tried it again yesterday, same mission, and everything just worked. No idea why it didn't work the first day, maybe something got a little screwy in the bindings that got cleared on re-starting DCS? Very strange though. Flies great. :D

Just tried this with some friends on my server and i couldn't get the thing to move at all on the ground. Tried 3 different spawns, no luck what so ever. Friends could take any of the planes and move no problem though. Controls seem fine, i can plant it on its nose with enough throttle and pitch, but it will rotate around the wheels... Brakes i can't see anything moving with, either inverted or not, but it does seem like they are on and super powerful no matter what i do. I tried removing/resetting all controls and it still wouldn't move. Gave up for tonight, will add some air starts and see if it locks up on landing later etc. Only differences from me and friends were: I was in VR, had the VR shaders mod, unlocked liveries mod, and a VR scene mod.

I assume similarly the bingo fuel and such audibles don't exist (as i've starved the cat a few times into the ocean so far). Would be neat if Jester went ahead and mentioned them though... as i think thats part of their job? Something simple like hey check that caution. Or were running on fumes...

I forgot that this was talked about even though i experienced two crashes tonight. I did some ground pounding first (aka lawn darts), no issues (game crash wise). Decided to do some intercepts. Engaged two F-16s, phoenixed both no issues. Engaged a bear, phoenix missed got close with sidewinder and guns, no issues. Engaged two MiG-29 (S i think), closed distance to around 25 NM i think and crash. Logged back in, re-engaged the MiGs, closed distance and crashed. Don't know if the MiGs launched at me, but i think they did lock me (without issue). F-16s definitely got closer than the MiGs, as did the bear, so its not just a distance issue.

Visually i'd say its maybe fine? Can't really tell if it is any worse. Performance is a tiny bit better, but it still stutters. Just shorter pauses. And this is after the update... Edit to add: i get around 40-50 fps most of the time according tot he in game meter, but stutter. I do see that 100% of my ram is in use (16gb). Will probably test with the smaller textures next.

MSAA is a in game setting. I am going to try turning that off for me tonight (had it on 2x). But to counter the likely jagged edges i will turn on AA in nvidia control panel. On the program settings tab i will put DCS.exe to have 4x AA, FXAA to on, and Antialiasing mode to override any application setting. The game itself doesn't offer FXAA, which is different sort of AA that should be fast. It only offers MSAA and SSAA, with SSAA being really much slower than MSAA. Thats just as a basis of performance comparison, i don't actually know what visual difference there will be, would have to test again and get screen shots to see. As long as it works better, and i don't notice anything odd though, i probably won't bother. That texture replacement stuff looks very promising too.

I have a 1060 6g as well and was having horrible stutter in the F14 (but not the F18 in the same mission). First test for me will be to drop msaa and force fxaa through nvidia controls.

When i get to that step and turn the repeater on (i think, i get the numbers being entered) i don't see any line like it says i should see...

Much of that would have to do with your FOV versus screen size/location/setup... And apparently racing simmers are way more picky about getting it right than we are. They even have calculators to get it right like this (or some built right into the game): https://andyf.me/fovcalc.html Might have to look into this stuff some more, this was just a little googlefu after remembering that the Stennis may be too short (its maybe 50 feet too short in game) but that wouldn't change it much. So i instead looked at why stuff is too small in sims and got a bunch of racing sim hits...

With both the HMD and NVG on, the parts of the info in the HMD display that overlap non-transparent parts of your plane (canopy bar, etc) is blurred. Rest of the info is fine. Feels very strange. Not sure if you should be able to use both, but i really don't see why NVG would ruin the HMD display at all, especially not only on non-transparent parts of your plane.

Is there a way to randomize the destination of normal units like you can with cargo carriers or spawning? As in spawn in zone A, B, or C and move to zone X, Y, or Z. I might be missing something obvious but i haven't seen it. Another one i am not sure of is if picking up cargo by command the best way to spawn cargo carriers already loaded?

Does the upcoming (eventually) dedicated thing need maps?

Its lovely. Easy to print and really quite nice feeling. Other than resizing some of the bearing fits (probably mostly to do with how my printer prints) and editing the lever arm (added a panel mount cable hole, lengthened, and keyed) it is as original. Might still have to get a little heavier springs, it centers just fine but it may be a little soft with the length of it now. Added the little sensor caps, the top girdle (bottom will mount to steel bracket) and a bracket on the front for a custom pcb with my pro micro. As is, the joystick feels way better than what i fly with (i'm cheap, its a pxn-2119) and since the logic will be the same (i replaced the boards in both throttle and stick with pro micros a long time ago, while doing other 'improvements') i think this will be a winner.

I assume that magnet is N/S on the faces? Other than taking a bunch more space that seems to be the same way i am doing it... I'm using 5 dia x 10mm long cylinder magnets (N/S on faces). The gimbal was a design i found on github. Tweaked it some, added some stuff to it. Made the stick based on pictures and trial. Printed it a few times so far to get to this model, which feels pretty nice... Ideally i can just unscrew that big locking ring and unplug the connector between gimbal and grip and change to something else later if i ever decide this is too fancy for whatever i'm flying. Sensor goes in that pocket on that disk thing, reads the magnet in the pocket behind. After the sensor, i just need to wire up the buttons and such (waiting on parts) and figure out a mount to attach it to my seat. Hopefully the 22.5 degree offset is right for actual use, not sure how much to lean it forward yet though. Some definitely feels better than none as i test it in my lap, but that isn't something critical to get right in model.

The KMA210 is also rotational, not linear. I have a magnet perpendicular to the axis and the sensor reads that. I actually wouldn't know how to use a linear sensor in a gimbal, but i haven't really thought about it before now either... Just looked for something rotational and cheap(ish) and ended up on the KMA210. Being of the DIY mindset i went ahead and got 10 when i started the project figuring i would make the stick (2 sensors), then maybe some pedals (3), maybe a throttle with nozzle/flap lever (3) and maybe a collective once i get bored with the 'easy' projects (last 2). Not knowing how to use it yet was not a limiting factor on going full steam ahead for me. I always just assume i can figure it out eventually and just keep at it.

My joysticks are all arduino/sparkfun pro micro clones, current one and throttle as well as this project with the KMA210s. I'd prefer to program the KMAs to the actual limits of my stick (more or less at least) instead of doing it in the sketch or just having windows calibrate it out just so the steps i do have (around 1/4 of the 4500 i guess) would be farther apart in voltage levels so the micro can read it more accurately. Not sure how good the onboard adc is for the current voltage steps, i didn't plan on using any more circuitry...

https://www.nxp.com/docs/en/data-sheet/KMA210.pdf Or anyone that understand its datasheet for the matter? What i would like to do on my project stick is to reduce the angle range (its 180 by default) to something more like 60 and set the zero to be somewhere around 150 degrees for it to sit better in the stick. Granted, i don't actually know if its even required, as i could probably just calibrate out the data in windows from whatever the sensor sends out... The sensor is still sending out the same resolution of data its capable of, its just up to the micro to read that accurately right? As opposed to limiting the range in chip, then i would get roughly Vdd to Vss on the data pin instead of whatever fraction i get now. I think i pretty much understand how to enter the programming mode and such in code, but the tables (page 25-26) for setting the zero and range just confuse me. I'll definitely work on doing it proper for now, i'm still waiting on some new switches for the stick as is so no flying with it yet. Any help with this chip would be appreciated though!

Getting a good visual key is important. I use the the top of the hud glass and the heading tape to trap the pod thing on the tanker. On run up it is basically needs to just touch to the top of the glass. After contact you need to keep it between there and the heading tape and it will be fine. The 18 also has auto throttle (ATC) but it just seems to make it worse for me, it either is too fast or too slow and then adjusting it is harder than just moving the throttle manually.

Since it had to be something on my end wrong, i pulled out the moose files from both my and the example mission and ran a compare in notepad++. Turns out i had ended up with an old moose file in my mission, but not the editor? (though i just downloaded the stuff a couple of days ago). New moose put in and it seems to be working fine. Just watching a troop deployment heli right now to see if it actually is gonna deploy, such excitement and i'm not even playing!

I'm starting to learn Moose to make some more lively missions for me, and one of the first things i wanted to do (after just random unit compositions each run of the map) was some AI heli troop drops. Looking at the example stuff i just went for the random deploy zones off the bat because why not. So i set 3 deploy zones, called Deploy 1, etc... and set my cargo/helis and loaded it up, breaking the mission entirely. DCS.log says: ".../~mis00001DD2"]:7: attempt to index global 'SET_ZONE' (a nil value)" Not sure what it was talking about (before i realized it had a line number there) i commented out all the cargo stuff until the mission worked again (thinking it was the nil in the pickup zone, since i wanted air loaded cargo). It ends up being this line: DeployZones = SET_ZONE:New():FilterPrefixes( "Deploy" ):FilterStart() So i added local to it, because it did say something about global. No change. I tried loading the Gori Valley mission, which has the same line basically in it, and it seemed to work just fine? local SetDeployZones = SET_ZONE:New():FilterPrefixes( "US Troops Landing Zone" ):FilterStart() Not sure what to do, as best i can tell i haven't done anything wrong?

Or they set a date on 'release' that they can guarantee so they won't get in trouble with steam for missing a more optimistic date like the 20th or whatever. Releasing early based on the steam date is not an issue though.

If you are loaded the 12 may not be enough trim for the trim warning not to come on too. There is a chart somewhere for x lbs to more degrees, i think it had a range of 16-19 on trim for light to heavy.

I just hope the pod is as usable from hotas as the one in the a-10 is. Comparing that one to using it in the harrier (without binding ddi buttons) is a night and day difference in effectiveness for me. Finding, identifying, marking, lasing, etc... I know i could bind ddi buttons to do it in the harrier, but it feels wrong.

I've been flying with my joystick and throttle as sparkfun/arduino pro micro clones for quite some time now. If you enable the option in dcs to sync hotas positions every switch is as you have them on the controls in game on once you get in the cockpit.