NewView - новый обзор в Ил-2

[wdq4587]

Hello Hurks

It is possible. NV can read only 6 axis. You can check all of this on Config/Joystic tab. Select Device # for Main devoce and look at the bottom panel. X,Y,Z,R,U,V values should changed if you change axis position and Device ID is correct. If axis you need do not working then it is not supported on NV.

X-36 only has 6 axis. The problem is the U vlalues in NV config tan never change. Others can change if you move the joystick. I also tested last night, using NV3.0 is same result. I want know your program use number or name to read axis values?

I don't installed driver for X-36 before in W2K. It's use microsoft default HID driver. Last night I installed basic driver of Saitek SD3.2. Still same result in NV.

Could you change Main and Additional joysticks? Send me INI file you using and describe correct ID for X-36 and Logitech joys.

That need I test it after I go home. But I guess that not INI file related. What I forgot last night is change joystick ID in W2K control panel to see the result.

NV has issue with analog zoom controlled by Additional joystick. I fix this on latest version.

I see.

About memry pointer problem. Exactly no Pointer problem is specified to C programmer style I use Delphi and Objects. I have no memory problems in general Do you familiar with DelhiX components for Builder or familiar with DirectInput?

I am not sure, you don't see pointer that do not mean there are no pointer, although I have used Delphi 10 years ago. I fell Turbo pascal and C++ is about same, what I changed to C++ Builder is because I do not like pascal syntax.

I am not familiar with DelhiX components or DirectInput. I do have some interesting on game programming but I really do not have time to try it.

No, this is not requared TIR HW. This used TIR interface for output zoom value to game. Z axis filled up with zoom value. Some games used this interface for contol zoom or move thru Z axis. For example "LockOn" or "GT Legends". FB do not used this interface. Only Key Generation output can be used for FB game.

I see. Thanks for explain!

SnapView is one more experimental kind of view on NV. It is like native Snap View on FB but this more flexible. For example this can track zoom position and correct change angle according zoom.

I see. I'll try it.

No. FB accept only values divide by 5. And I do not like this interface on NV. This is very FB specific and not comfortable.

If they can allow any number, that should be great. I don't understand why they restrict FOV values numbers in DeviceLink interface. I mean only limited kind FOVs, why not a set(gov) instead so many call. I guess it's not difficult to support any FOV (in range) in graphics engine.

I do not understood. Sorry. Please describe more detailed and sendINI file.

I should say it simple. What I mean is if I try use KG4 but no KG1 KG2 KG3 assigned first, it will not work in NV3.6 (later version I have not tested).

Thanks for your reply!