Activity for Roman Ludwicki
-
Roman Ludwicki created merge request #360 on FlightGear
Unification of labels for aircraft ratings
-
One more update from me. I checked how it works on Windows 11 and here I have no problems, rudder works fine. As far as I can see here the “Linux Event input” list is empty. So the problem seems to occur only on Linux, ranguli is using PopOS, I'm using Linux Mint 21.3
-
I have a workaround. In my case, I need to disable event input by using the option: --prop:bool:/sim/input/no-event-input=true and rudder starts working as it should. Why do we need the event input? I can also disable hid input --prop:bool:/sim/input/no-hid-input=true because it doesn't do anything in my case, only the log info disappears: 9.59 [ALRT]:input can't open InputDevice Saitek Saitek Pro Flight Rudder Pedals_0
-
Hi. I have the same issue. A few days ago I noticed a problem with my “Saitek Pro Flight Rudder Pedals” controller in the next version. I always have the rudder tilted to the maximum left. In the “Joystick Configuration” window, I can see that everything is working properly, when I move the pedals, axis 2 responds in a range of values from -1 to 1, but the rudder still remains in the same position, maxed out to the left. Clicking the “Reset Configuration” and “Refresh Joysticks” buttons does not...
-
Hi. I have the same issue. A few days ago I noticed a problem with my “Saitek Pro Flight Rudder Pedals” controller in the next version. I always have the rudder tilted to the maximum left. In the “Joystick Configuration” window, I can see that everything is working properly, when I move the pedals, axis 2 responds in a range of values from -1 to 1, but the rudder still remains in the same position, maxed out to the left. Clicking the “Reset Configuration” and “Refresh Joysticks” buttons does not...
-
Setting own tower position doesn't work
-
Setting own tower position doesn't work
-
This must be merge together with https://sourceforge.net/p/flightgear/fgdata/merge-requests/327/
-
This must me merge together with https://sourceforge.net/p/flightgear/flightgear/merge-requests/351/
-
This must me merge together with https://sourceforge.net/p/flightgear/fgdata/merge-requests/327/
-
Add logic to enable/disable Start and Stop buttons in Video Control view
-
Add logic to enable/disable Start and Stop buttons in Video Control view
-
Update to version 1.5.1
-
Fix possibility to translate description for scenery version
-
Fix possibility to translate description for scenery version
-
Fix possibility to translate description for scenery version
-
I checked on 2020.3.19 I added options: --prop:/sim/fgcom/server=fgcom.ddns.net --prop:/sim/fgcom/selected-server=fgcom.ddns.net I selected fgcom.ddns.net in the FGCom settings window. Unfortunately the crash still occurs, the only difference that I had to make more clicks on the COM1 buttons than before. In my opinion, the server address does not matter here.
-
Update to version 1.5.0
-
Releted to https://sourceforge.net/p/flightgear/fgdata/merge-requests/318/
-
Related to https://sourceforge.net/p/flightgear/flightgear/merge-requests/335/
-
Fix restart sim for keep the same aircraft when user has installed more aircrafts with the same code
-
Fix restart sim for keep the same aircraft when user has installed more aircrafts with the same code
-
Add ListView canvas widget
-
Related MR in fgdata: https://sourceforge.net/p/flightgear/fgdata/merge-requests/317/
-
Related MR in flightgear: https://sourceforge.net/p/flightgear/flightgear/merge-requests/334/
-
Add option to hide the aircraft on the map
-
Add option to hide the aircraft on the map
-
Update completion scripts
-
Related to https://sourceforge.net/p/flightgear/flightgear/merge-requests/332/
-
Related to https://sourceforge.net/p/flightgear/fgdata/merge-requests/315/
-
Fix calculate temperature for ISA METAR scenario
-
Fix calculate temperature for ISA METAR scenario
-
Fix calculate temerature for ISA METAR scenario
-
Fix run Launcher with --restart-launcher option when user did not specify --launcher option
-
Disable fullscreen mode for QT Launcher window by using `--disable-fullscreen` option
-
This change is needed for https://sourceforge.net/p/flightgear/fgdata/merge-requests/314/
-
Requires: https://sourceforge.net/p/flightgear/flightgear/merge-requests/329/
-
Update -h -v output according to boolean options with optional values
-
Add support for `<optional-arg>` in help output
-
Fix types name conflict on Windows platform
-
OK, I changed ParamType::BOOLEAN on ParamType::VAL_BOOL
-
Add unit tests for boolean options and space as value separator
-
Fix `BOOL` conflict name on Windows platform
-
Depending on https://sourceforge.net/p/flightgear/simgear/merge-requests/124/
-
Add new string utils functions: `is_bool` and `to_lower`
-
Update version to 1.8.5
-
Update to version 1.8.4
-
ready for testing
-
Update to version 1.8.3
-
it's not ready yet
-
Extend command line options
-
Fix --min-status option
-
Parametrize development years
-
Parametrize development years in Launcher
-
Parametrize development years
-
Fix calculate temerature for ISA METAR scenario
-
Yes, without my proposal fix the crash still occure.
-
Add `/environment/atmosphere/is-isa` property for ISA METAR
-
https://sourceforge.net/p/flightgear/flightgear/merge-requests/320/
-
https://sourceforge.net/p/flightgear/fgdata/merge-requests/310/
-
Add ISA METAR scenario
-
ISA metar scenario
-
Add Logbook addon
-
It doesn't seem to matter which frequency I click. It crashes on every one. But it does indeed matter how fast I click the buttons. The faster the more likely the crash. crash after 3-4 clicks, faster than once per second crash after 4-7 clicks, once per second crash after 8 clicks, once every two seconds
-
The callstack which I obtained is: (gdb) where #0 0x00007ffec40008d0 in () #1 0x00005555564ac1f6 in iax_xmit_frame (f=0x55558b030960) at /home/romek/Pobrane/Apps/FlightGear-2020.3-build/dnc-managed/flightgear/3rdparty/iaxclient/lib/libiax2/src/iax.c:906 #2 iax_reliable_xmit (f=0x5555843ead50) at /home/romek/Pobrane/Apps/FlightGear-2020.3-build/dnc-managed/flightgear/3rdparty/iaxclient/lib/libiax2/src/iax.c:906 #3 iax_send (pvt=pvt@entry=0x555571a5c430, f=f@entry=0x7fffffffc740, ts=ts@entry=0, seqno=seqno@entry=-1,...
-
Segmentation fault during select freq with enabled FGCom
-
I see, it's not very configurable and not useful for attaching other widgets. That's true.
-
OK, renamed
-
Add ListView canvas widget
-
Prevent from closing the simulator just because it can't write to the logger file
-
Upgrade to version 1.8.1
-
Too bad, but I handled it for myself in another way. Every minute I save the data to a separate file. When FG closed by [X], then on restart, the first thing I do is read the recovery file. The plus side is that the user will not lose data even during a crash (loses 1 minute at most :)) The downside is, there has to be an additional timer running in the background.
-
Signal exit when close by [X]
-
Hello, I just merged your patch, thanks!
-
Add possibility to call ls2 telnet command without dir parameter (like for ls command)
-
Replace displaying in Launcher `--on-ground=false` to `--in-air` for on final
-
I flew a UFO near EPWR and I normalized the RAM consumption between 20-26 GB by use Medium preset for graphics quality and reduce slider Maximum number of aircraft and scenery tiles cached to min value 100. I think this slider can be crucial, because before that I always used the maximum value of 10000 and the memory consumption only grew. Now, for the first time, I've noticed that memory is being freed up and not being fully consumed (I have 32 GB), but around 23 GB is still a lot. EDIT: I also...
-
I flew a UFO near EPWR and I normalized the RAM consumption between 20-26 GB by use Medium preset for graphics quality and reduce slider Maximum number of aircraft and scenery tiles cached to min value 100. I think this slider can be crucial, because before that I always used the maximum value of 10000 and the memory consumption only grew. Now, for the first time, I've noticed that memory is being freed up and not being fully consumed (I have 32 GB), but around 23 GB is still a lot.
-
My UFO EPWR test still leaks memory. I also tested your WS30_FSWeekend on EHAM and there I have memory leaks as well. My screenshots in attachment.
-
I debugged the code a bit to see how it looks. When we click on an carrier in the Launcher, it runs the LocationController::setCarrierLocation(QString name) method where the name parameter is the name of the carrier, e.g. Eisenhower. This name is then searched in the CarriersLocationModel structure to finally get a CarriersLocationModel::Carrier object from CarrierVec that contains, for example, mScenario as the scenario file name (e.g. eisenhower_demo). I thought this could be our identifier. However,...
-
This is probably a different case, however. Here it's not a case of duplicate scenario loading, it's the inability to find the right aircraft carrier by having its name duplicated in two scenarios (XML files).
-
This is probably a different case, however. Here it's not a case of duplicate scenario loading, it's the inability to find the right aircraft carrier by having its name duplicated in two scenarios.
-
AI carriers issues when loaded from menu and repositionning
-
Double name of Eisenhower carrier in scenarios conflicts with each other
-
Fix segfault when using `--fgviewer` command line option
-
I confirm, 32 GB RAM consumed in a few seconds and Linux hangs
-
In my opinion, Docs/README.local_weather.html is very technical (describes the algorithms) and https://wiki.flightgear.org/Weather is more useful for someone who just wants to find out what the options do.
-
Update default `log-level` as `alert` instead of `info`
-
ok, thanks, merged
-
Update default `log-level` as `alert` instead of `info`
-
i18n: update Polish translation
-
i18n: update Polish translation
-
Use the correct GUI members for the Data Distribution Service example
-
Add Polish translation to org.flightgear.FlightGear.desktop file
-
For the good of the reader, it would be better for him to see the keyboard shortcuts untranslated than not to see them at all. So I prefer the second option, but only for the tables.
-
It's hard for me to find an official acronym, but indeed KPH is a common one, so it's OK for me.
-
Fix using SI units like speed in km/h and altitude in meters for flight plan in Launcher.
-
I was thinking of something like that, but if there are problems with spacing, it's not worth pushing into it. Alternatively, I would just insert the missing key bindings in English into the other languages so that this information will not be omitted.
-
I do not want to stop you, so we can leave these translations of the rows, I just think that would be better for the readers, but no problem. Maybe I will back to that when I have time. As for the \tS and \tE macros, they can stay for me if it is to help readers see the untranslated text.
-
Polish version looks OK, thanks!
1 >