Menu
▾
▴
#2202 mouse control problem
Hello, my mouse TAB control for the wheeler always had all the screen space to move around, and i could fly confortably with good ground and air control, but suddently the cursor began to work only in the center of the camera, kind of reseting its position when reaches some threshold around the middle of the screen, and so it has been much harder for me to control the plain either in accelerating and lifting. I have reinstalled this version of the game twice with the same problem still happening.
windows 10
2018.3.5
radeon rx 570
problem have acurred with different aircrafts at different airports
i have used the default aircaft, the f16, and default scenery
option:console =
option:aircraft-dir = C:/Program Files/FlightGear 2018.3.5/data/Aircraft/c172p
option:aircraft = c172p
option:airport = PHNL
option:launcher =
Using default download dir: Path "C:/Users/jtorg/Documents/FlightGear"
read-allowed path not found:Path "C:/Users/jtorg/Documents/FlightGear/AI"
read-allowed path not found:Path "C:/Users/jtorg/Documents/FlightGear/Liveries"
Using TerraSync dir: Path "C:/Users/jtorg/Documents/FlightGear/TerraSync"
EmbeddedResourceManager: selected locale 'en-US'
Using stock OSG implementation of GraphicsWindow
initializing cloud layers
Enabling ATI/AMD viewport hack
Configuration State
============= =====
aircraft-dir = "C:/Program Files/FlightGear 2018.3.5/data/Aircraft/c172p"
fghome-dir = "Path "C:/Users/jtorg/AppData/Roaming/flightgear.org""
download-dir = "C:/Users/jtorg/Documents/FlightGear"
terrasync-dir = "C:/Users/jtorg/Documents/FlightGear/TerraSync"
aircraft-search-paths =
scenery-search-paths =
C:/Users/jtorg/Documents/FlightGear/TerraSync
C:/Program Files/FlightGear 2018.3.5/data/Scenery
Image loading failed:Warning: reading "C:/Program Files/FlightGear 2018.3.5/data/Aircraft/c172p" not supported.
ATI Technologies Inc.
Radeon RX 570 Series
4.6.13587 Compatibility Profile Context 20.2.2 26.20.15019.19000
4.60
Splash screen progress loading-aircraft-list
Starting automatic scenery download/synchronization to 'C:/Users/jtorg/Documents/FlightGear/TerraSync'.
Splash screen progress loading-nav-dat
Splash screen progress init-scenery
picking entry # 3, server is https://dream.t3r.de/fgscenery
terrasync scenery provider of the day is 'https://dream.t3r.de/fgscenery'
General Initialization
======= ==============
FG_ROOT = "Path "C:/Program Files/FlightGear 2018.3.5/data""
Attempting to set starting position from airport code PHNL heading 270
Reading timezone info from: Path "C:/Program Files/FlightGear 2018.3.5/data/Timezone/zone.tab"
Selected scenery is tilecache
FGStgTerrain::init - init tilemgr
Initializing Tile Manager subsystem.
Initializing the tile cache.
max cache size = 100
current cache size = 0
done with init()
Splash screen progress finalize-position
sync of https://dream.t3r.de/fgscenery/Models started, queue size is 26
Splash screen progress creating-subsystems
Creating Subsystems
======== ==========
Reading materials from C:/Program Files/FlightGear 2018.3.5/data/Materials/regions/materials.xml
Successfully synchronized directory 'Models'
sync of https://dream.t3r.de/fgscenery/Airports/L started, queue size is 25
Successfully synchronized directory 'Airports/L'
sync of https://dream.t3r.de/fgscenery/Airports/K started, queue size is 24
Reading systems from Path "C:/Program Files/FlightGear 2018.3.5/data/Aircraft/c172p/Systems/systems.xml"
Initializing HUD Instrument
Reading sound sound from Path "C:/Program Files/FlightGear 2018.3.5/data/Aircraft/c172p/c172-sound.xml"
Creating subsystems took:6450
Splash screen progress binding-subsystems
FGPropertyManager::GetNode() No node found for hydro/active-norm
ignoring unknown axis-alignment'yx-plane'.
ignoring unknown axis-alignment'yx-plane'.
ignoring unknown axis-alignment'yx-plane'.
Volcanic activity off.
KMA20 audio panel initialized
Hobbs system stopped
Hobbs system stopped
Starter off
KI266 dme indicator #0 initialized
Electrical system initialized
Astro Tech LC-2 Chronometer Loaded
Primer reset to 0
Garmin 196 loading cities
Garmin 196 loading cities done
Related
Hi Joao, is this a new problem tht occured when you installed 2018.3.5? And do you know what verion you were using before, which did not have the problem?
Hello. I have installed only the 2018.3.5 before i reported this problem. I
did unninstall the 2018.3.5 and installed the 2019.1.1 today, but the
problem was still there so i installed the 2018.3.5 back again. I think i
remember this began to happen while in-game , after i pressed some
combinations of keys - in the 2018.3.5.
James Turner jmturner@users.sourceforge.net escreveu no dia domingo,
12/04/2020 à(s) 10:46:
Related
Tickets: #2202
Hi, I just downlaoded 2018.3.5 for macOS and I don't see this on my machine, so I will ask some other people to test the build and see if anyone else has the same issue. There always was some code to keep th emouse inthe centre 50% of the screen, but it doesn't seem to be active for me.
Just to be sure, you said: " I think i
remember this began to happen while in-game , after i pressed some
combinations of keys - in the 2018.3.5." .. so when you first start the application, the mouse works okay?
And then later, after some time / key-presses, it starts behaving weirdly?
That's quite important, since we will need to figure out which keys it is, to fix the problem.
Hi. Yes, i first installed and played this game, the version 2018.3.5,
about 5 days ago. I then played few times with no mouse problem - the
cursor could run around all the game sreen after i pressed TAB, selecting
the wheeler mouse control mode. About the next day, or some hours later, i
started to play again, taking-off in the f16. I could taxi fine, using only
the mouse to turn sideways. I could take off fine, only using mouse to turn
upwards. When i reached some altitude, i pressed some combination of keys,
searching for another view of the aircraft, believing it was shit+V, and i
believe i pressed another completly different set of keys because i am
still used to the controls of another different flight simulator (FSX). It
was then when the mouse began to behave strangely, not reaching all the
sreen and being blocked around the middle of the screen, and lot letting me
turning the plane - it will most likely spiral downwards toward the ground.
Today, in addition to this mouse control problem, i noticed my HUD does not
move around when i look around anymore as before, and so its static in
front, of the plane. Strangely, the boing 777 its the only plane which the
HUD static problem does not happen.
James Turner jmturner@users.sourceforge.net escreveu no dia domingo,
12/04/2020 à(s) 14:33:
Related
Tickets: #2202
FlightGear 2020-04-12 17-32-49.mp4
https://drive.google.com/file/d/1qO4AQOQOFNBuOMgZm5oHj9ZWAk80-TIW/view?usp=drive_web
Hi again. I made a video to try demonstrate the problem. Is this video, we
can see the mouse problem at the begining of the game - the cursor resets
some position around the middle of the screen, but does not reset its axis.
Later, when i am about to take off, i can not control the wheeler in any
way. This is another problem i have noticed today, with all aircrafts, but
it eventualy would let me control of it again after some time or pressing
some keys. I had so to taxi and taxe off only using the keyboard num keys.
Also my loading screen have been always bugged like this, but it wil load
with fine graphics only if i select RESET at the menu/file.
joao silva negsus@users.sourceforge.net escreveu no dia domingo,
12/04/2020 à(s) 17:19:
Related
Tickets: #2202
More symptoms:
Some more info to Jonathans report:
Its from a Mac user.
Flightgear 2020.1.1
Aircraft: 172p and 777
Control input: mousepad
Additional comment 1: "its better than 2020.1.1rc but sometimes like it just doesnt react to my imputs"
Additional comment 2: "the same issue happens when im on mouse to look around mode"
on macOS there's a new issue caused by an OS update, that moving the mouse 'ourselves' (back to the center) now triggers a security alert and can be blocked. I'm considering to disable this logic on macOS completely to avoid the security warning.
However, the origin report here was from another OS, so I wonder if there is something else going on.
On Windows 10 personally I never noticed any difference whatsovever.
Original reporter on Mac:
"yes but it was my privacy settings, now its good"
So that at least is resolved.
I cannot reproduce the issue in the original post at all.
Okay, that fits what changed in Catalina: we need to maybe change the default behaviour on macOS since the system privacy settings do matter.
Hi folks, is anyone able to provide any updates on the status/validity of this issue in 2024.1 and up?
I tested again and still have the same problem
ranguli ranguli@users.sourceforge.net escreveu (segunda, 21/10/2024 à(s)
20:30):
Related
Tickets: #2202