Bog9y

Hi guys, Just formally raising the bug of the offset function. I haven't got screenshots or a trackfile because this bug is easy to check but if it's absolutely needed I can make those. So, to test the TCN offset function I am parked at Kobuleti with TRUE unboxed on the EHSD and do as follows: 1) Tune Senaki TCN 31X 2) note BRG and DME to the TCN , for example 005 degrees at 20 nm 3) create OFFSET from TCN with BRG 185 and range of 20 nm 4) select T/OS steering and note radial and bearing to the offset waypoint. It should in theory be 0 nm but it will read something like 4 or 5 nm to the east. To fix this you have to apply DOUBLE the variation of the map. At Kobuleti the magnetic variation is 6ish degrees E. So in this example we have to add 2x6 = 12 degrees to the bearing in order to get the T/OS to be at the correct position. When you do this with the example above and put in a bearing of 185+12 degrees = 197 you will get a T/OS that's 0.1 or up 0.3 nm away. This leads me to believe that the VARIATION has been applied in the wrong direction in the coding of this function. If you use TRUE on the EHSD the variation has to be added only once to get the correct offset position. The same happens when you create a WAYPOINT OFFSET. Quickest way of testing this is by placing a waypoint exactly on the TCN station and performing the same steps as for the T/OS function test above. This also happens on the Syria map and Nevada but in Nevada the error is much bigger due to the bigger mag variation. The TAC-000 manual states: 1.12.6.4.6 Waypoint Offset Entry. The waypoint offset range and bearing can be entered to the nearest hundredth of a nautical mile (0.01 nm) and tenth of a degree (0.1), respectively. The ability to enter waypoint offsets using a magnetic reference is available. The waypoint offset bearing entered is interpreted as a magnetic reference if the map menu (MAPM) TRUE option is not boxed. If the TRUE option is boxed the waypoint offset bearing will be interpreted as a true bearing reference from the waypoint. If the waypoint offset bearing is entered in magnetic reference and then TRUE is boxed, the waypoint offset bearing will update as local magnetic variation changes.

Hmmm, interesting. I just tried it on the Caucausus, Nevada and Syria map and switching to true does change it by the varition but it's still off. The way I test TCN offset is tune the TCN, note bearing and DME. Create offset from the tacan with that bearing and dme and it ends up being 4 nm off. Using TRUE still makes the offset waypoint 2 nm away. Something doesn't add up. It's similar in Syria (because the variation is similar) but in Nevada the difference was something like 20+ nm. I also added a waypoint right on top of the TCN station and did the same offset tests, same result.

Just bear in mind that the bearing for offsets seems to be bugged (definitely in the Caucasus map), where you have to add double the variation to get the correct bearing from a waypoint/tacan. I haven't raised a formal bug yet. May do it later today.

Agree, hope this can be fixed.

Good point! I'll amend the title

I've not heard of that. Does it give you a performance boost?

Thanks! We can only try and keep our fingers crossed.

Here's the link: https://explore.amd.com/en/technologies/radeon-software-fidelityfx-super-resolution/survey

Here is the link: https://explore.amd.com/en/technologies/radeon-software-fidelityfx-super-resolution/survey

Hi guys, just installed this mod. I like it a lot! The only problem is , for some reason my jetpad seat doesn't vibrate with this mod. Does anybody know how to get it working? It works with the T45 mod and every other module. I searched in this forum but found no answer. DISREGARD!: I GOT IT WORKING. I had to install the BETA version of SimShaker for Aviators, it doesn't work with the stable version.

This was in December and my first 3d print, I've learnt my lesson since. Hopefully Thanatos reads your suggestion before he starts his print.

Hey dude, I tried amending the nozzle lever thickness with fusion360 and after several attempts I gave up. I'm not good with fusion360 and found it too frustrating. The next time I broke the nozzle lever I just used a double ended steel screw to connect the lever at the breaking point. So far it's stayed in place without problems, several months now. I think I laid the casing on it's biggest flat side, I can't remember to be honest, it's been a while since I did it. EDIT: actually, if you look at my pic above you can see that I have lots of excess PLA stuff on what is the front part of the housing (the opposite side of where I'm holding it). So that was my orientation.

AWESOME! Thank you!

I would assume that if an airfield has a specific pattern altitude you have to comply with it. Logically your downwind leg may extend a little bit and the descent rate from the 180 to the 90 would be steeper if it's a higher alt. For a 1000 ft pattern the 180 to 90 section would be done with a 5 degree FPA. The procedures for the higher pattern alt are described in the USMC FSG.

Bumping this thread from 6 months ago. I'm just trying to get my head round the NSEQ and TOT features and feeling confused. I am wondering about the following: 1) To enable NSEQ on the moving map (after entering the IGRS/EGRS and/or TERM waypoint in the DATA page) you need to press OSB 10. This used to be NSEQ I believe, but now it's called ROUTE. Is this a deliberate change to the naming of the function to avoid confusion? Or did I do something wrong and is ROUTE something different than NSEQ? 2) With NSEQ/ROUTE enabled I can only use WINC up to the TERM waypoint or the last waypoint of the IGRS route. It will not go beyond that. Is this the way it should be? It seems a bit strange to not be able to WINC to the next waypoint after you have hit your target. You would need to switch to MAP, press ROUTE and then WINC works again. 3) If the target point is the last waypoint of the IGRS string then what should the TERM waypoint be? 4) Fangsout mentions that in the jet the route would auto sequence the waypoints if you wanted it to. How does this work and is it possible with the RB module?

Disregard, it was user error. I'm not sure why but my installation went wrong. I used OVGME and that worked nicely! Thanks

Yep, I'm part of the "crash on exit of a mission" - club too now. Great

I tried it with a mission set in June, not sure why but to me the grass looks far too bright / vibrant. Nothing like the screenshots I've seen. Not sure why?

Hawkeye, can you post what the mission profile , speeds/alts and loadout was for your test? I looked but I'm useless with Discord.

Ok, so I'll hold off until the new release. Thanks

Can I just confirm that the spring and summer textures are finished and will not change with the next release (which I believe is in the next few days)?

Ah , that will explain why I cant see it! Thanks

I've seen this mentioned a few times now, guys say "see my sig for my pc specs". But...how can I see their signature? Is there a setting I can change or is it supposed to be on their user profile?

Can i ask, what GPU have you got and what are your DCS TEXTURE and TERRAIN TEXTURE set to? I have a 2080 Super with a Reverb G1 and 2nd mission loads would sometimes crash and when they didn't crash the performance would be crap. So here is what I've done and so far it works really well: 1) STEAMVR and WMR4SteamVR change from BETA to STABLE or LKG 2) Remove any overclock on GPU/CPU 3) Change textures to MEDIUM (from HIGH) and TERRAIN TEXTURES to LOW (from HIGH) , delete FXO & Metashaders folders I get good performance now on 2nd mission loading and no crashes so far. I think the crashes/performance issue was related to VRAM somehow. No idea what or how though.

I had another play with it and as suggested to me by some smart guy I tried using TOT whilst in A/G mode. I confirm that the TOT function works in A/G mode and gives a sensible command speed in TAS. The timer on the UFC scratchpad should count down but it doesn't , it's stuck at the time to go to the TOT when it was entered. So using A/G is a work around at the moment but the TOT function should be fixed and work in NAV mode too. Perhaps the issue is the conversion from TAS to IAS?