Jump to content

Recommended Posts

Posted

And people think TM’s Target software is too complicated .

 

I have tried to mess around with it such as adding button input to the brake axis, and the way to achieve this is quite convoluted and really not user friendly. This app is most definitely made by engineer rather than software designer (no offense to engineers out there).

PC: 5800X3D/4090, 11700K/3090, 9900K/2080Ti.

Joystick bases: TMW, VPC WarBRD, MT50CM2, VKB GFII, FSSB R3L

Joystick grips: TM (Warthog, F/A-18C), Realsimulator (F-16SGRH, F-18CGRH), VKB (Kosmosima LH, MCG, MCG Pro), VPC MongoosT50-CM2

Throttles: TMW, Winwing Super Taurus, Logitech Throttle Quadrant, Realsimulator Throttle (soon)

VR: HTC Vive/Pro, Oculus Rift/Quest 2, Valve Index, Varjo Aero, https://forum.dcs.world/topic/300065-varjo-aero-general-guide-for-new-owners/

Posted
And people think TM’s Target software is too complicated .

 

I have tried to mess around with it such as adding button input to the brake axis, and the way to achieve this is quite convoluted and really not user friendly. This app is most definitely made by engineer rather than software designer (no offense to engineers out there).

 

A much easier way of doing this is to use the 'AxesToButton' functionality. Go to axis 8, set it to Edges1, Zone 1, set it to a percentage point that you're comfortable with (ie 25% will press the button when you've pulled the brake lever three-quarters of the way, 0% will press the button only when the lever is pulled completely to the end of its travel), and set it to an unused button. Remember to click the checkbox in the top left to enable the AxesToButton content you customised. Et voila! You have a button! If you are really set on not using the analogue axis of the brake, you can go to the Logical Axes tab and hide the axis. Don't disable it, that will stop your button from working - just hide it from the HID. Tada! You now have a button that activates when you pull the brake, and no analogue axis to confuse your game.

 

http://forum.vkb-sim.pro/viewtopic.php?f=27&t=2868

 

I had no trouble following the above to add a button to my brake lever axis.

The first post in that thread is somewhat convoluted, the post a little further down I copied above makes it easier to do, at least it did for me.

Don B

EVGA Z390 Dark MB | i9 9900k CPU @ 5.1 GHz | Gigabyte 4090 OC | 64 GB Corsair Vengeance 3200 MHz CL16 | Corsair H150i Pro Cooler |Virpil CM3 Stick w/ Alpha Prime Grip 200mm ext| Virpil CM3 Throttle | VPC Rotor TCS Base w/ Alpha-L Grip| Point Control V2|Varjo Aero|

Posted

It is complicated. Designed by an engineer. Also making it much more flexible & customizable than if features were hidden to make it more user friendly.

 

I too have had little problems getting it to work how I want after finding the correct guides. I document what I did to make it work so I don't have to look it up again next time.

 

Sent from my Moto Z Play using Tapatalk

🍺 Snack Officer  🥨 
Intel I9-10850K (OC @ 5.0ghz) │ 64GB (4x16GB) DDR4 3200 │Gigabyte RTX 4090 Gaming OC 24gb
- ҉ - Blackshark Cockpit Trainer - ҉ -    Thread   | Download

Posted (edited)
http://forum.vkb-sim.pro/viewtopic.php?f=27&t=2868

 

I had no trouble following the above to add a button to my brake lever axis.

The first post in that thread is somewhat convoluted, the post a little further down I copied above makes it easier to do, at least it did for me.

 

Oh I know how to do this now, but that isn't the point. This might be fine if you are an engineer or love to do complex things, but a lot of people would beg to differ. From consumer's stand point, what I'd like to see is simplification--a button or option that says add button input to brake axis. And when you click on that in the tool app, boom, done. Why do I need to bother with axis 8, edge 1, zone 1, etc. It sounds cool but most people do not really want to deal with that and would rather have it done from behind the scene.

 

That button on axis function is actually the easiest thing to do, now try to program this thing to have macro function, toggle switch, tempo, etc. and lets see how many people can do it.

Edited by Supmua

PC: 5800X3D/4090, 11700K/3090, 9900K/2080Ti.

Joystick bases: TMW, VPC WarBRD, MT50CM2, VKB GFII, FSSB R3L

Joystick grips: TM (Warthog, F/A-18C), Realsimulator (F-16SGRH, F-18CGRH), VKB (Kosmosima LH, MCG, MCG Pro), VPC MongoosT50-CM2

Throttles: TMW, Winwing Super Taurus, Logitech Throttle Quadrant, Realsimulator Throttle (soon)

VR: HTC Vive/Pro, Oculus Rift/Quest 2, Valve Index, Varjo Aero, https://forum.dcs.world/topic/300065-varjo-aero-general-guide-for-new-owners/

Posted
Oh I know how to do this now, but that isn't the point. This might be fine if you are an engineer or love to do complex things, but a lot of people would beg to differ. From consumer's stand point, what I'd like to see is simplification--a button or option that says add button input to brake axis. And when you click on that in the tool app, boom, done. Why do I need to bother with axis 8, edge 1, zone 1, etc. It sounds cool but most people do not really want to deal with that and would rather have it done from behind the scene.

 

That button on axis function is actually the easiest thing to do, now try to program this thing to have macro function, toggle switch, tempo, etc. and lets see how many people can do it.

 

 

+1

 

The root of complicated processes reduced so the average user can interpret and implement. Systems are designed for those that do not tech speak but utilize them. Project managers are trained to convert tech speak into simplified terms for executives and users and in terms of end-results.

Posted
Everything seems a lot easier to me with the latest version of VKBcfg vs the one I was using in April

Great to hear it, thank you!

>

Best Regards from VKB Lair,

AeroGator

Posted

Yeah the software isn't so easy, but jeez is it powerful. It has taken me a good deal of time to get my head around some of the basic stuff and now moving onto more avanced features.

 

I've had a lot of problems with mismatches between firmware and the VKB_Joy, so I run a very old version

 

Would I want it changed certainly not, it's a fantastic piece of software that exends the usage of the stick enormously. With my old version some things are quirky and some just don't work as described................So what, don't use them and move on

 

Is there not a simpler version available anyway?

 

Good grief when I started to use it there wasn't even an Englsh manual

 

BUT I still love it and a significant amount of effort must have been made to develop it and I applaud VKB Really Loudly for doing so THANK YOU VKB

Posted

The software is indeed powerful.

My problem is trying to figure out what to choose as there can be several options.

 

I personally would like samples of how to configure certain fundamental procedures similar to how the TM manual shows examples for their script programming. I mean examples shown in a subset all together.

 

With samples, I can substitute and try different options but without examples, I am completely lost.

 

That's just me but I suspect there are many others in the same position.

 

Thanks for a great product overall. I'm looking forward to the day when I can configure the stick - and upcoming throttle, the way I want them to work - not relying on the SIM program to do that.

 

Thanks again.

Posted
I personally would like samples of how to configure certain fundamental procedures

Our home forum has tons of in depth talks about programming, plus it is the place where our engineers check in on nearly daily basis.

My advice would be to get registered there, and spend some time on reading the tech support threads.

SEARCH function sucks there - and we know it - but we'll be back to smaller problems like tuning up the sites once we release TECS.

>

Best Regards from VKB Lair,

AeroGator

  • 2 weeks later...
Posted

The software is powerful, but it is confusing at begin. It takes time to get head around where to go to do what.

 

Once the basics are familiar, it is powerful and easy.

 

Easy to use != Easy to learn

i7-8700k, 32GB 2666Mhz DDR4, 2x 2080S SLI 8GB, Oculus Rift S.

i7-8700k, 16GB 2666Mhz DDR4, 1080Ti 11GB, 27" 4K, 65" HDR 4K.

  • 2 months later...
  • Recently Browsing   0 members

    • No registered users viewing this page.
×
×
  • Create New...