RogueRunner

not just TMS AFT, tried CZ on the radar and on the TGP MFD. Is the masked issue a bug?

I understand that if you designate something with the TGP in PRE mode an offset is created. My problem is I cannot marry up the steerpoint and the TGP again afterwards in PRE mode however many times I press CZ. Something else I need to do? Pressing CZ ini NAV mode will reset the steerpoint to the correct place but the TGP never points to the steerpoint again unless I change delivery modes. This means essentially I can drop things in PRE mode once, since I can never get the TGP to look at a steerpoint or HMCS designation again it's almost impossible to deliver something in PRE again. I'm sure this is just operator error but I canoot figure it out.

Still happening, changing the spawns to 'start from ground' is a workaround.

I get that sometimes binding will just stop working. Had it on the F16 and now it happens quite regurly for me on the M2000. In the 2000 today my PTT buttons stop working, trying to bind anything to these buttons does not work again. If I jump into a Hornet which uses the same buttons on my warthog for PTT it works. Only way to make it work is to delete the throttle config and rebind everything again. Happend twice today on the 2000, like I said, happened previsouly on the Viper but never again after I deleted the config file.

what exactly did this entry in the patch notes fix? Before the patch I had to press CZ OSB on the ground radar to reset the nav waypoints after creating a SPI. The HOTAS CZ function did not do this. I could never figure out from the posts if this was intentional and working as is or a bug. The above entry I thought was to address this but it still is not working.

Track file Notice how the time to impact reaches zero and then it still takes about 5 - 10 secs before the bomb arrive. Sorry about the views, was not using headtracking for this one. gbu24.trk

I looked but could not find a way to move one radio to receive on the left ear for example and the other radio in the right ear. Is this possible?

Yeah sorry, language thing, I mean the time to impact timer is way off. It will reach zero and the bomb might only hit about 5 to 10 sec later Will post a trk ASAP

It's not accurate, not even close. Is this correct or stil a WIP?

For me also, now that I read the mini updates thread I get how it works, however switching from VIS/DTOS to PRE and doing a TMS aft short does not do a CZ, clicking the osb on the TGP does however. Another thing for me is the TGP is in different operating states between NAV mode and A/G mode. In A/G mode it was active but switching to NAV mode it's in STBY mode.

I've seen exactly this using the HAD after targeting a sam. Cursor zero do nothing.

Something went awry with the options.lua When I deleted that file it started working

My dedicated server ignores this in the autoexec.cfg and starts up with 8088 even if I specify 8089. Confirmed with netcat that port 8088 is open and 8089 is closed. Any ideas?

Currently the Voice Callsign Label is assigned whichever next callsign is up for grabs in the mission editor, ie first F16 is normally Enfield so this will become ED. If you change the callsign you have to manually edit the label in the Datalink tab. Very easy to forget to do this that can lead to confusion later in the mission Would be great if this can change automatically as you change the callsign for the group.

It will obviously come out when I am out of the country, hence anything from the 17th till the end of the month! You guys can bet on that!

Yeah I know, it's the trouble finding it again when you make it 'alive'. The confine to gme window obviously do not keep the mouse in the window so very frustrating.

The mouse pointer gets 'lost' quite often for me. Seems like it 'times out' and disappear and when you want to use it again it's difficult to find it. Moving the mouse and hoping it passes in your fov is the only way but many times I am unable to find it again. Left clicking in most cases result in the treaded 'window not in focus' message. This is with a Quest 2. 'Cursor confined to game window' is enabled in the VR options screen but obviously does not work

Apache FCR seems likely to me as well after the Apache datalink video by Wags showed the FCR running at the start.

Happens on my dedicated server every so often. No VPN and internet is rock solid.

Same with the Q2 so I just open scratchpad as well and use it's target marker to designate a point on the map

airbase:getWarehouse() local storage = airbase:getWarehouse("Goulet") --storage=STORAGE:FindByName("Goulet") storage:AddLiquid(STORAGE.Liquid.JETFUEL, 10000) Why does this give me a attempt to index global 'airbase' (a nil value) stack traceback: error? EDIT: was using the wromg version of moose.

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