All Activity

One of the UK national archives docs has some blue vixen stuff

The USAf version used the flying boom.

I’ve had exactly the same thing happening to me. I’ve had to shut down the computer to get out of it. Don't have a clue about pagefile sizes or how and what to mess with. I’ll keep an eye on it, good luck Razor

Part of the base game/UH-60L... designates whether the pilot or co-pilot has control priority for multicrew aircraft. Not an Armed Blackhawk addition.

Frankly, I’m shocked that there isn’t more chatter in the forum about this. Maybe most people aren’t aware yet, or maybe I’m overlooking it. Either way, I’m away from home until tomorrow but I’ll be installing it first thing. Thank you so much @mbucchia

Thanks. I guess it's the following line within function default_fighter_player(t), correct? limits_6DOF = {x = {-0.050000,0.4500000},y ={-0.300000,0.100000},z = {-0.220000,0.220000},roll = 90.000000}, No. I am looking for the camera position limits when moving the camera, not just the snapview limits.

So…….. upon careful re reading of documents…… I am enlightened to my past mistakes The sensor changing without using the knob switch is only in interaction/cooperation mode, (duh!!!). So let’s say you lock someone from TP scan mode and want to IFF. Best way is to select cooperation. Select fox 1, then un select it after seeing “C” or not. Or could switch fox1/coop sequence. Let’s say you enter lock from TP vertical scan, helmet, OPT, but don’t want to STT too long, you’ll have to lock with cooperation off. When you’re ready to IFF, select cooperation to see IFF status then switch coop off or it will keep giving them STT as long as laser range is present. Same with TP scan or even gun mode, inside 6.5 km, once it gets a laser return radar just locks (now that it’s not needed for ranging). And HUD will show radar mode.

and what does it say about the analogy with the P-27? That's right, nothing

This might help?

Asking here on the unlikely off chance anyone might have a working, no longer needed, pcb from inside the seat I might be able to buy? I've already spoken to Andre and he's been very helpful, but unfortunatly unable to source another. As you can see from the photo attached, mine has seen better days. This is my last stop before I board the train to convert the seat to an arduino shakeit system and use it for simracing only with simhub, or completely dump it and shell out for an HF8

Still Broken.

Thanks for the write up LOL - I've got to tell you "Moira" had me googling for a while before I realised what it would be... " Moiré " Moiré pattern - Wikipedia & on this: Is that the same idea as foveation?

The boxes should be beige or tan when everything is alright. Double check that Petrovich has reported weapons ready, and otherwise circle for a minute or two. P.S.: Besides the preparations of the sights, the missiles themselves need to warm up for a few minutes before use

Bumping. It feels to me as if the module can only turn about 90 degrees to the left or right before it hits an invisible turn wall. I am unable to do a 180 degree turn at all. Anything after about 90 degrees and the module steers back the other direction.

You forgot the hard part: finding a dev who'd pick up the Buccaneer. I imagine the Jag would sell, and I sincerely hope someone will pick the Harrier (any of them) up eventually, but other aircraft have a very low chance of happening now that RAZBAM is probably done with DCS (which is a pity, because they were also doing the Lightning). AFAIK, Harrier in particular was a problem because of its very much classified radar (and sure enough, the one we have is a radarless USMC variant). It's the reason RAZBAM gave for making a US Harrier variant. Specifically, they were unable to acquire docs for the Blue Vixen and Blue Fox radars. A British variant would require at least one of this, and even Blue Fox was apparently asking too much. I think the Marconi RWR might've been a problem, too. Sure, it's not every aircraft that's affected, but the Brits are very stingy with their military documentation. I imagine Buccaneer's Blue Parrot would be considered less sensitive than either of those.

I mean there is not enough time in the day to fly em all . I’ve got plenty of ‘time’ on type now though. Those that I fly frequently. If I don’t mess about and rush in I can bring most of em in nice and smoothly now (he says, oof) Feel sorry for my Jets really, prolly the most neglected of all modules and OH, I just remembered, how could I not mention it? THE OH! OH-6A, THE LOACH!, I fly the Loach and the Loach flies me . The most fun to be had in a flight sim.

Thought this feature was close ED as per one of your Friday newsletters. What happened?

Done so I believe I was doing the tutorial so yeah and made sure weapons were active the boxes were yellow/beige so It should have worked

Is The Way working with the Kiowa Warrior?

Server.lua, but must be used as template and copied to saved games/dcs/config … do not modify the template

Snapviews.lua? [emoji6] Sent from my SM-A536B using Tapatalk

I use Quaggle's Keybind Injector, but I still truly hope that ED adds more of these missing binds. Here is what I personally add to my own control config: return { keyCommands = { --HUD {down = 3002, cockpit_device_id = 7, value_down = 1, name = _('HUD Mode Grid'), category = {_('Ins HUD controls'), _('Custom')}}, {down = 3002, cockpit_device_id = 7, value_down = 0, name = _('HUD Mode Day'), category = {_('Ins HUD controls'), _('Custom')}}, {down = 3002, cockpit_device_id = 7, value_down = -1, name = _('HUD Mode Night'), category = {_('Ins HUD controls'), _('Custom')}}, --Targeting {down = 3001, cockpit_device_id = 11, value_down = 1, name = _('Laser Standby Switch On'), category = {_('Ins Targeting Mode Controls Panel PVR'), _('Custom')}}, {down = 3001, cockpit_device_id = 11, value_down = 0, name = _('Laser Standby Switch Off'), category = {_('Ins Targeting Mode Controls Panel PVR'), _('Custom')}}, {down = 3002, cockpit_device_id = 59, value_down = 1, name = _('K-041 Targeting System Power Switch On'), category = {_('Ins Targeting Mode Controls Panel PVR'), _('Custom')}}, {down = 3002, cockpit_device_id = 59, value_down = 0, name = _('K-041 Targeting System Power Switch Off'), category = {_('Ins Targeting Mode Controls Panel PVR'), _('Custom')}}, }, axisCommands = { {cockpit_device_id = 7, action = 3001, name = _('HUD Brightness')}, {cockpit_device_id = 8, action = 3002, name = _('IT-23 display brightness')}, {cockpit_device_id = 8, action = 3003, name = _('IT-23 display contrast')}, {cockpit_device_id = 23, action = 3001, name = _('Helmet device brightness')}, {cockpit_device_id = 46, action = 3006, name = _('ADF Volume')}, {cockpit_device_id = 49, action = 3002, name = _('R-828 (VHF-1) Radio Volume')}, } }

As a workaround until a "moving" seat is implemented, just move your camera up and down.

There is, so it's bad etiquette dropping it here, but the problem with the Pimax forum is that the only reasons to go there are that you are a so enamored with your Pimax that you have to write about it all the time, you're having trouble with your Pimax and want help, or you're thinking of getting one & want opinions- & none of those groups are the people I wanted to ask. It's like looking for reviews of a product online - you only get the very ends of the distribution of user experience. If you buy it and it does what you expected to the level you expected, there's nothing to motivate you to write a review. What I wanted was answers from people that have one & now just use it without issue having found the sweet spot that means it's a background device not an ongoing hobby in itself. Even putting it in the Chit Chat sub-forum means that probably only 1/1000 forum visitors will ever see it, & some of the 999 who don't will be Pimax users who could answer the question... Ironically while sub-forums make navigation easier, they also make for topic ghettos.

Hi SilverDevil, Thank you for digging into my problem. I have changed the pagefile now so Windows is managing it. Gonna test it out and see how it goes. Will report back. Thank you for your help.