|
|
Caucasus_Map_UR_Radio_issue.jpg (127,550 bytes) |
|
|
0153NEc1 update fixes problem with ground altitude conflict. http://tacnoworld.fr/universradio-download/ |
|
|
Please note I made an error in the versions I listed... The most recent occurrence was with one aircraft (KA-50) using 0.1.5.2-NE and the other aircraft (Mi-8) using 0.1.5.3-NEc1. The Mi-8 was using the v3.0 relief map; I'm not sure about the KA-50. If you want us to test specific versions / airframes / altitudes / areas etc let me know. |
|
|
"If you want us to test specific versions / airframes / altitudes / areas etc let me know." Yes it's great. Just install 0153NEc1 (or newer) over 0152NE, then talk between JTAC/RW (with or without relief map, now it isn't important anymore) Many thanks. For information range is here : http://tacnoworld.fr/universradio/simplified-principles/ |
|
|
Can you state what you are looking for? Where it happens? What happens? Ranges / airframes / altitudes? Basically: the 132nd primarily use the area of the map indicated in the attached jpg ("132nd_working_area_caucasus.jpg"); we have only encountered the issue described in the area indicated in the first attachment. I know it happens between aircraft (A10s, KA50s, Mi8s), and I know it is still possible to communicate with an ATC controller using LotATC ATC radios and "located" in a AWACS aircraft flying at around 40000ft. |
|
|
132nd_working_area_caucasus.jpg (228,526 bytes) |
|
|
Only simple feedbacks ( 0153 NEc1 and newer) With 3D location where comms were. (LatLong Alt) After I can debug comms from these locations, and get if it's cut by relief or overrange, etc or bug |
|
|
Hi Tacno We did some testing on Thursday but I'm not sure how useful it will be... We had three participants: 1: AWACS at 39k feet, using LotATC and ATC radios 2: A10-C at 4k feet 3: KA-50 at 2k feet Basically: we tried to be methodically about it and have one aircraft hold a position while the other moved. However, both aircraft reported a break up of reception / introduction of static - but usually not at the same time; mostly one was clear when the other was not (occasionally they reported break up / static at the same time). It also happened "randomly" e.g. there isn't a line where the comms problems start, but they come and go within the area - and it can go either way; e.g. aircraft in location A can no longer hear aircraft in location B (but B can still hear A), and then it flips with very little movement by either aircraft. Just to note: nearly all the time AWACS could hear everyone and everyone could hear AWACS (the AWACS aircraft was an a wide orbit overhead), but there was a period where AWACS lost comms with one of the aircraft. We marked up DCS as we went along, and I will upload those screen grabs in a bit (they are on another PC), but I'm not sure how much use they will be because the issue is so "scattered" across the area. However, it will give you a rough idea of where we were operating. |
|
|
Screen_180621_203332_tracks_marked.jpg (2,430,315 bytes) |
|
|
Screen_180621_203315_south_detail.png (936,031 bytes) |
|
|
Screen_180621_203325_north_detail.png (1,060,895 bytes) |
|
|
Three new images uploaded: "Screen_180621_203332_tracks_marked.png" the full area DCS screen print marked up with notes and AWACS route (39k ft) "Screen_180621_203325_north_detail.png" northern detail of above "Screen_180621_203315_south_detail.png" southern detail of above Notes: IAF.AssafB (callsign BEAST) = A10C pilot, at 4k ft Donkey (callsign DRAGON) = KA-50 pilot, at 2k ft 132nd.evilivan = CTRL; AWACS controller (LotATC and ATC radio) Where the mark has been made by 132nd.evilivan, it refers to the aircraft position not the AWACS position... Unless specified, comms comments refer to VHF (127.100) We were also using FM (32.9), and when comms were lost on FM that was noted Really not sure how much value all this will be, but that is what we did! |
|
|
... Summer just started and a good harvest already begins ... Thanks Evilian, I'll debug with your feedback (LatLong you noted) Does a player with 0151NEc1 have a cut of comm. ? If yes, the 0151NEc1 doesn't work. |
|
|
I confirm that all three of us were using version 0151NEc1. |
|
|
Could you attach your \Saved Games\UniversRadio\log folder in a zip pls ? |
|
|
All of us? Or just mine. I will do it when I get home. |
|
|
yours only as you had cut comm |
|
|
A misunderstanding there - we all had cut comms, at different times. It wasn't consistent. Pilot A would stop hearing pilot B, but pilot B could still hear A - and every combinations (between three of us) you can think of. Does that make sense? Would like you the logs from all three of us? |
|
|
AssafB_log.zip (3,039 bytes) |
|
|
I uploaded one log file; for two of us there were no log entries for the day in question, so didn't seem worth sending those (but let me know if you want them). |
|
|
If you want and have time, we can generate verbose log files for helping us to debug. If yes, reply to me at universradio[at]tacnoworld.fr |
|
|
A bad file of heights gives issues with the Caucasus Relief Map V3. Meanwhile, the previous v2 can be used. http://tacnoworld.fr/UniversRadio/download/install_UR_CaucasusMapv2.0.exe |
|
|
I'll do deep tests before closing |
|
|
fixed and released |
- Anonymous
