tolgamat

The stretching effect isn't that one affected by wrong res or aspect settings. It's definitly affected by the angle of view while zooming.

To do what? That settings are working to provide the NVG-viewport in a comparable ratio and position as like the normal cockpit-viewport. Sir, yes, Sir! Just like described in topic 1, Sir!

Hi Guys, as i tried out the NVG-mode first time since using multi-monitor-setup in cause of TP, i also had to realize the "broken" optics. I also didn't find how to affect the NVG's resolution or aspect ratio to the screen. But i found out, that it's affected directly by the settings related to the main window. The offer is no real solution, just a workaround, avoiding the "stretched to the left NVG-optic", by filling up the hole available screen-area with cockpit-view. So if you want back your NVG in a suitable kind, do as follows: 1. Rearrange your monitor-setup, so that the touchscreen is located under the main-screen and middled out between left and right cornor. As i use a 2048x1152 main and a 1280x1024 touch-screen, the position of the second should look like x=(2048-1280)/2=384 and y=1152. 2. Regardless of using TB or TP (i'm using TP, ...Documents/Touchpal/touchpal.xml), position in x,y should be the same like above: x=384, y=1152. 3. For Monitor-Setup there has to be following rows according to monitor-arrangement and TP: Viewports = { Center = { x = 0; y = 0; width = 2048; height = 2176; viewDx = 0; viewDy = 0; aspect = 0.9411764705882353; } } Shkval = { x = 384+20; y = 1152+20; width = 640; height = 480; } ABRIS = { x = 384+751; y = 1152+241; width = 480; height = 640; } 4. Change relevant rows in options.lua as like this: ["aspect"] = 0.9411764705882353, ["width"] = 2048, ["height"] = 2176, ...et voila. The only thing is, the pivot poit of head moving seems to be a little bit displaced downwards... maybe someone will find out what and why... what effects the main screen getting stretched verticaly when zooming. Btw, using this setup without TP, i mean by directly using the clickable cockpit of bs has it's own charme, even if it's not as comfortable in some situations. regards tolgamat

After getting solved my #1 issue concerning BS and G940 here's #2. As we know BS offers to modify the output of the input (sound funny, doesn't it? :megalol:) of the control axis, for example of the x and y joystick-axis. This seems useful for me, as i'd like to use a non-linear reaction, alowing small deflections in inner regions and an uprising deflectionrate when moving the joystick to outer regions. And as i really love the ability of using FFB in BS (no FFB = no reason to play flightsims), i'm interested in fitting the joysticks position to the behaviour of the simulated cyclic stick. Actually this seems only to be accurate when the input-curve of the x and y axis are linear and having a growth rate of 1, meaning the saturation in both axis beeing the same. In case of defining an output-curve, the forced joystick deflection doesn't fit to the simulated cyclic-stick position after using the trim function. For me it seems like the FFB-curve stays linear while the output-curve has been modified. I'm wondering how to set FFB behaviour fitting on a defined output-curve. Any idea? Btw, setting trim-forces and vibration forces doesn't effect the issue.

Thank you Dimebag1, that was the simple and effective solution.

Hi there, first let me introduce myself: i'm playing BS since release but never gone for a serious virtual career like in a squad or so. Just having fun and modding. I really love the atmosphere in BS with my hands and feet on the G940, giving additional commands by touchpal and kpow's profile while having a glance over all by freetrack. Startup procedure: I don't know if there is any relation to it, but let my tell about. The procedure starts with connecting the WiiRemote by BT, starting Freetrack and checking functionality. Then connecting the G940, opening the profiler and checking functionality also. At last starting and checking touchpal. If everything is fine, like it is normally, i go on with starting BS, choosing a mission and go on for a flight. So far so good. Problem: While playing, for short or long, the G940 will quit working in BS with a reliability of 100%. The throttle lights are still on and the FFB-pressure on the stick feels the same like last but BS doesn't recieve any more commands of the hotas, nether of the axis set in BS nor the buttons set in profiler. When pausing the game and switching back on desktop the profiler is still working and shows all functions of the system working accuratly. The only thing helping out for the moment is shutting down the profiler, starting it once again (restarting not just reopening from the taskbar) and switching back to BS. After that everything works fine for some minutes, just until the command line gets broken again. That can happen after some minutes, second or just not. The real annoying factor is when restarting the profiler and in the same moment freetrack quits communication with the WiiRemote. Any idea?