Longbow Gold (Win 10 native with nGlide)
Вставка
- Опубліковано 27 вер 2024
- Another quick test video to compare dgVoodoo2 with nGlide.
Controls the same, using the same DxWnd config.
This time using nGlide v2.10 as the Glide wrapper. Using the DirectX backend in nGlide, as the Vulkan backend just CTD's as soon as you start a mission.
Very stable, just one crash when switching to external view as the tutor is speaking, which was always a bit iffy when running in Win10.
Oh and you get to see all the on-base bits as well.
nGlide plays better with GeForce Experience recording, except the screen is stretched horizontally (was aspect correct on the monitor).
👍
Good work getting this classic up and running
Well it's up and running, still not perfect and still some work to be done, which is why it's on the testing playlist, but getting there!
I have a question, it is not relevant for LB but I am getting out of options. I saw that in your blog you have many ideas on how to seup hotas on old dos games . in soome old games throttle axis is not supported by the simulator but instead the + / - keys are used, often on top row, close to number 0 on main keyb. How do you emulate with hotas, and without target? I tried with gremlins and joy2key and have no success
Excellent question, I have to give a more complete answer later, but when I played F-19 and F/A-Hornet 2.0 which used +/- keys I used the throttle hat buttons under my thumb rather than a throttle axis.
@@darkenedroom which is what i mostly do in the situation. But i would like to use the throttle
@@Gabriele-bu7ri (1) the more I think about the more I'm thinking it may be deserving of its own article on my website. So, you're probably looking at throttle axis banding. Using profile software to split the throttle axis into bands. So for a simple example, axis is configured with 3 bands, + key is mapped to the top band of the throttle, middle band does nothing and - is mapped to the lower band. The problem being that your throttle will pump out keypresses when it's within the band, so you'll probably want to make then key holds (simulates key held down).
(2) However, if the bands are wide then moving the throttle within the band changes nothing, the key is still held down, it's only as you move from one band to another that a change occurs. So if you're in the top band thrust is increasing, as you pull back the thrust still increases as you're still in the top band (which is very counter intuitive) it's only as you move into the middle band that thrust stops increasing and it will only start to decrease as you enter the lower band. The wider the band the less precise your throttle control will be.
So you could limit this by limiting the banding to very narrow bands around the centre and filling the remaining unallocated axis space with dead bands so you end up with:
Wide dead band (does nothing) -> Narrow band above centre (thrust increase) -> Medium centre band (does nothing) -> Narrow band below centre (thrust decrease) -> Wide dead band (does nothing)
This ensures that there is only short travel from thrust increase/decrease to middle do nothing, limiting the counter intuitive action. How narrow/wide they should be will be a combination of personal preference and sim response.
What's really needed is to program a profile with a motion of travel so pushing forward is a + key hold, stopping releases the key (thrust unchanged) and pulling back is a - key hold. But to do that you'll need to look into the advanced programming section of Gremlin to see if it's possible and there's the risk that depending on sim response, the centre point begins to move to an end of the axis (e.g. you have to pull back more to decrease than pushing forward to increase, eventually leaving you stuck at the bottom of your throttle axis).
I wish I had an easy answer for you, when I've looked into throttle banding, I haven't been impressed with it, as an answer with any of the profiling software I've used. So for now I'm finding buttons a more intuitive control scheme, until I delve into to serious controller programming!
What do you mean with " the on base bits"
The base screens which you can see at 0:09, with the Pilot, Campaign, Single mission, Instant action, Historical missions and Exit to operating system options. You couldn't see those in the previous video as MS GameBar wouldn't handle the switch from the base screen to the flight engine with the Glide wrapper I was using.