RogueRunner

Feels like the nose is tied to a rubber band in the vertical axis. I see it in all phases of flight.

Timecodes available.

Same here. We get this weird time warp back and forth thing going until the wso leaves and everything goes back to normal instantly. Also had a cockpit desync last night when I joined the back seat after he took off. Radar showed off on my side while it was def on for the pilot.

yes

Anything I need to do extra to run a Sinai mission on a up to date dedicated server? Once added to the mission list it's ghosted and cannot be selected to run.

A headsup would have been nice

Also yesterday flying on a Snowfox server which has hotstarts, I entered Khasab tower on the VHF, 124.35 if memory serves, and when I tried contacting them through the ATC menu my pilot did not even started the conversation, using the UHF frequency on the red radio worked 100%

You have to be inside one of the supported aircraft before it will connect.

in the editor when putting down and aircraft there is a 'civil plane' tick box on the armament tab. What does that do? Logic tells me it would not get engaged in conflict but then this is DCS and it does

There is issues with it in Voice Chat also

seems a few of these are on the 'back burner' as it were, the GBU alignment one also seems not to get attention

another request, for VR after you use the S+C+T to transfer the current WP into the jet, can the app delete the list automatically? MY experience last night was I flew around, used C+S+S to save the point, using the scractpad hack ofcourse since the circle is not visible in the Quest 2, and transfered it to the F16. Then later added another target but if created the whole list again in the INS computer. EDIT Scratch that, I see there is a C+S+D to delete everything

Very useful app but it does not display the cursor on the F10 map on Quest 2 VR headset. The cursor is visible on the 2D display. Everything else seems to work though, just no way to get the correct coordinates in the Q2.

ignoring the handbag fight, so does VC support the intercom?

The CBU-105 will not align if you are not in A2G mode and the weapon is not selected. It will stop at whatever it was when you deselect the weapon or exit A2G mode. This might be as it is IRL but seems odd.

doesn't work, OA1 or OA2 you can cycle only to wpt 25, not higher. Also cannot enter something higher than 25 via the ICP

lemme go try with OA2, thx

Seems you cannot use waypoints higher than 25 to create OAP's Is that a feature? My thinking is to create an OAP for something I cannot see but I know it's brg/distance from something I can see. The quickest way would be via a markpoint

mine did the same. After a clean install still crashed and after about the 3rd time I removed the saved games folder it just started up again. I have no idea what changed.

I looked at the traffic on my dedicated server and I see traffic to one specific IP (138.201.206.135) on port 8090 only when the server is running. Nowhere can I find documents why the server is trying to talk to this IP on this port. Is this known traffic or must I investigate further?

That is a VRAM issue. You get that bar at the bottom on the quest 2 when you run out of VRAM. The Q2 does not recover VRAM when it's not needed anymore. Only thing really is sto restart the game. Some people said a ALT TAB to another task and back solve it for them.

Is this suppose to work? Tried testing it tonight. Could not get it to work. The Voice chat window would not even show the frequencies for the radios until you move the mode dial all the way to G and then back to M. If it does work could someone post a quick guide?

A refresher flight we did on the SAAF discord last night. Just some navigation, AAR and using offset waypoint to drop bombs.

I also like to know. Everybody falls back to ground attack points and such. From a pure navigation point of view, in the Mirage for instance you can tune to a TACAN channel and create an offset for 200 degress and 70nm and the INS will give you steering to follow to reach that point. Navigation beacons in the DCS world is sparse so it makes sense to make offset waypoints to enter a valley or some other point you want to fly to. The Viper OA1 and OA2 can do this for waypoints but you can only enter feet which obviously makes the range an issue, you would most likely only be able to put in a few miles at best. EDIT I guess with modern systems you do not need this much, it pertains more to older INS systems. Would still have been nice to do, for example if you get a bullseye call ffrom GCI for ground targets it would have been easy to program the offset from bullseye to get to that target

i suppose the 8GB limit is not a *thing* anymore with the release of South Atlantic. Nevada is a very nice map to fly around I must say.