Sprool

did some more testing. On Farp capture I spawn in ammo truck and fuel truck to drive to the farp using late activation. THen I can land the huey there, repair, rearm & refuel, so although it remains red in f10 and assigned to redfor, its usable by blue. So maybe it IS working ok, only the F10 map label is bugged

Is the lack of farp colour change a more recent bug then? Youtube videos I watched are from a couple of years back

Im not even at the stage of getting it to function, just the ownership never changes, it stays red and part of the red coalition. When you watch other videos on farp capture, including Suntsag's, the farp changes colour and alliegence changes. Even on the simplest mission just setting up an unarmed red farp, then driving a blue tank in triggers the message but farp does not change colour or alliegence, and it should do!

I'm struggling with capturing a farp, I set up the simplest possible test, a red farp and a blue tank just out of range. The tank then drives towards the farp and the triggers work - I get "Red Farp Captured" but the farp never turns blue. I run the identical test but on an airfirld and it works fine.

OK cheers - all sorted.

When i set up custom snap views in the F-14b, I jump into the F-14a and they are back at default.

Is there a way to copy over all the control keymapping (Hotas, keyboard, others) from the F-14b to use in the F-14a model without reprogramming manually everything already set up in the F014?

i dont really have a problem with Master Warning, alt and att hold, I can figure those out. At least we got the QFE making sense again

The texture file in question has no text on it - only the numbers - and swedish numbers are same as english you can see this from the image I posted up earlier.

..or just copy over the default texture from the dcs mods viggen default cockpit texture folder as per earier comments above ^^ !

LNS_VIG_CPT_UV05.rarheres the default one, I had to zi it up as it was >4mb, it sits in Eagle Dynamics\DCS World OpenBeta\Mods\aircraft\AJS37\Textures\ and it needs to be put into Eagle Dynamics\DCS World OpenBeta\Mods\aircraft\AJS37\Liveries\AJS37cockpit\English\

...if I can find them....

I found a solution, in the texture file LNS_VIG_CPT_UV05.dds I reversed the numbers indicated - originally was 9 on the left through to 0 on the right, this sorts out the issue in the English cockpit mod. You can find the file in ED>dcs world open beta>mods>aircraft>AJS37>Liveries>AJS37cockpit>English (Note: I added a yellow colour to help me detect the correct part of the texture file to edit - attached edited texture file at the bottom) LNS_VIG_CPT_UV05.dds

You are correct, turning the knob anti-clockwise in default cockpit turns the dial hands anticlockwise and increments the numbers downwards, in the english cockppit turning the knob anticlockwise turns the dial anticlockwise but increments the numbers upwards. COuld this be cured with an edit to the relevant lua file entry?

Is anyone else getting the wrong QFE pressure on the ground when using the English Cockpit Mod? (8992 and it should be about 1002)

Yep bomb bay drops work fine as before, nothing changed. WIng bombs still bugged in MP

Apologies if already reported - I searched first and found nothing. I have a few skins for the Mossie with different coloured spinners, they appear fine as expected when props are not turning but as soon as engine starts they return to default grey. Any cure or workaround possible?

Many thanks!

I need to free up a drive and move all my dcs/saved games stuff to a differnt ssd. Its about 77Gb worth of mods and liveries. How can I move it so DCS still recognises it and accepts the new folder path?

so great to see one of my favourite fsx planes born again in dcs, and with the awesome CBU-97's - what's not to love?

Bare Metal USAF skin just loading into DCS files area.

RAF Trainer skin for the Tucano

I had a couple of missiles go stray, they were still flying 25 minutes then they finally made it to the edge of the map and stopped suspended in mid air for the next hour till I exited the mission

Ive had success in PP mode, fire-n-forget but in TO mode heading towards a waypoint teh screens are not picking up the targets I want near to the wp, so its impossible to say if the self-guidance works. I can TDC-depress, move the corss hairs then the screen unfreezes but all I get is green and grey splotches. Watching the missiles home in on PP mode the screens work fine. Note: The designated target WP is positioned about 200 ft from a couple of Hercules on the apron of a runway so should be very clearly visible. Having watched videos from Spud, Wags and Cap I'm following exactly the same workflow but failing.

looks like repair and purge fixed the issue with the default spit liveries