Activity for OpenRadar
-
Kerry Pick created ticket #11
403 Forbidden error loading OSM data
-
New incarnation of the FGCOM server is now active on fgcom.ddns.net. I have added functionality in the rear end of this server to accept all frequencies dialled into it (geolocated to within 100nm of a fixed position still as this is a feature of the clients). As long as all participants are on the same frequency EXACTLY and in close proximity to each other, they should hear each other.
-
Papa Charlie modified a comment on ticket #10
I did follow the instructions, extracted the .zip, moved into the folder and ran ./OpenRadar.sh I noticed I get the exact same error when I run java -jar OpenRadar.jar
-
I did follow the instructions, extracted the .zip, moved into the folder and ran ./OpenRadar.sh
-
Wolfram Wagner posted a comment on ticket #10
<meta http-equiv="content-type" content="text/html; charset=utf-8">Hi. It looks like you are starting the plain JAR file. Please follow the installation steps in the guide. You require to extract the ZIP. Mit freundlichen Grüßen Wolfram Wagner Am 01.06.2023 um 07:01 schrieb Papa Charlie <vibromax@users.sourceforge.net>: [tickets:#10] Get error running OpenRadar on Linux ( Fedora 38 ) Status: open Created: Thu Jun 01, 2023 05:01 AM UTC by Papa Charlie Last Updated: Thu Jun 01, 2023 05:01 AM UTC Owner:...
-
Get error running OpenRadar on Linux ( Fedora 38 )
-
Benedikt Hallinger posted a comment on ticket #5
FYI: Mumble 1.4 was released, and FGCom-mumble reached stable too: https://www.mumble.info/blog/mumble-1.4.230/ https://github.com/hbeni/fgcom-mumble/releases/tag/v.1.0.0
-
Missing Taxiways & Parking Number
-
I have fixed this in the original coding. I am reworking it a bit in the moment. Thanks for bringing this up!
-
Michal Dziczkowski posted a comment on ticket #9
Hello @wwagner. I think that it would be a great idea if the .jar would have already the structure inside, that the OpenRadar could work as an out-of-box solution. Greetings.
-
[Bug report] jar issue
-
Hi, the JAR is not run-able by itself, without the directory structure. Please extract the ZIP file and run OpenRadar from there. https://wiki.flightgear.org/OpenRadarDownload Have fun! Wolfram
-
[Bug report] jar issue
-
Also, the current and future FGCOM clients uses --server= and not --voipserver= as executable arguments. Worth updating OpenRadar to use --server= executable launch argument instead of --voipserver=.
-
Keyboard shortcuts and FGCOM restart not working
-
OpenRadar sound
-
Support 8.33kHz frequencies
-
Hello Benedikt, Sorry, I was too busy to care about OpenRadar for a while. It's not the additional zero in the decimal formatter that I just added, it's that i did not look into the OpenRadar code for a while. After a OS change and two reinstallations I had to set up my dev environment at first... Thanks for your patience and your pull request patch. The next update release will support the third decimal place. Best regards Wolfram PS: I was not aware, that the radio feature is still in use. Fin...
-
I applied Capt_Jeffs fix and it works. Patch attached.
-
Missing Taxiways & Parking Number
-
Patch attached
-
Patch attached
-
I implemented this: https://github.com/FlightGear/openradar/pull/2
-
Implemented in PullRequest: https://github.com/FlightGear/openradar/pull/3
-
With the latest commits, the plugin supports different "identities" which are derived form the UDP client port. Trough this, OpenRadar may support several radios out of the box, when supplying the plugins port as "FgCom ports" in the settings multiple times. To implement it, each Radio string UDP packet should have its own (stable) source client UDP port. This will yield different "identites" mapped in the FGCom-mumble plugin, and such no interference/overwriting of the COMs to each other. Alternatively,...
-
With the latest commits, the plugin supports different "identities" which are derived form the UDP client port. Trough this, OpenRadar may support several radios out of the box, when supplying the plugins port as "FgCom ports" in the settings multiple times.
-
For details refer to https://833radio.com/news/show/7
-
Support 8.33kHz frequencies
-
Support FGCom-mumble
-
Linux shell script enhancement - start from everywhere
-
Richard Harrison created ticket #3
MP models Version 2 packets problem with ORCAM
-
The latest update fixed this issue. Reason behind was a changed sound api. Please replace your JAR, if you have it installed already.
-
OpenRadar released /Latest release/OpenRadar.jar
-
-
Tim Dicus posted a comment on ticket #2
Thanks! That cured the notifications. I haven't tested FGCom yet.
-
Andreas Vogel modified a comment on ticket #2
You can disable sound processing by icedtea: sudo bash nano /etc/java-8-openjdk/sound.properties comment out lines with icedtea remove comment character from lines with com.sun.media.sound Your file should then look like: #javax.sound.sampled.Clip=org.classpath.icedtea.pulseaudio.PulseAudioMixerProvider #javax.sound.sampled.Port=org.classpath.icedtea.pulseaudio.PulseAudioMixerProvider #javax.sound.sampled.SourceDataLine=org.classpath.icedtea.pulseaudio.PulseAudioMixerProvider #javax.sound.sampled.TargetDataLine=org.classpath.icedtea.pulseaudio.PulseAudioMixerProvider...
-
You can disable sound processing by icedtea: sudo bash nano /etc/java-8-openjdk/sound.properties comment out lines with icedtea remove comment character from lines with com.sun.media.sound Your file should then look like: #javax.sound.sampled.Clip=org.classpath.icedtea.pulseaudio.PulseAudioMixerProvider #javax.sound.sampled.Port=org.classpath.icedtea.pulseaudio.PulseAudioMixerProvider #javax.sound.sampled.SourceDataLine=org.classpath.icedtea.pulseaudio.PulseAudioMixerProvider #javax.sound.sampled.TargetDataLine=org.classpath.icedtea.pulseaudio.PulseAudioMixerProvider...
-
OpenRadar sound
-
-
Chat messages are not recived when pilots use new protocol
-
Solved in updated OR.
-
-
Chat messages are not recived when pilots use new protocol
-
The new multiplayer protocol is not supported in the moment. I am working on it already. Supporting being visible, reachable and being able to chat in two protocols at the same time forces me to rewrite a good part of the protocol. I will try to fix all spots where FGFS and Openradar have diverted and release it, as soon as I am convinced it is stable again.
-
merspieler created ticket #1
Chat messages are not recived when pilots use new protocol
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
1
