All Activity

To be fair the aircraft itself doesn't have a gateway function the AWACS and other assets do. You're also making assumptions based on limited or no data. ED folks have said the gateway is modeled others have said it's not so who knows what is/isn't actually going on. Personally I think if we can't see client aircraft data on the TAD through the gateway we shouldn't see AI aircraft data. Keep it the same for both then it removes any confusion.

I know that at the moment there won't be any paratroops on launch (until ED adds them) But can we transport troops inside? even if for now there's maybe no visual model yet, it would be great to transport troops to and from an airbase/FOB. But i guess that wouldn't be possible unless troops are part of the warehouse system. Might have to CTLD troops in the meantime between points. Just a thought I had

I actually want to keep this behaviour as it allows rapid Targeting of the SPI from the HMCS. Nate

I doubt a big radial engine like this would be so fragile, seems overdone.

Hello again, Due to the ongoing bug with the CH47 Chinook CDU where the screen goes blank while trying to access certain pages, or the page doesn't change, I have modified how the waypoints are entered. I have removed the ACP entries, so now the LAT/LON coordinates are entered directly into the FLPN/ALTN FPLN pages. I believe this solves an issue that can pop up when two or more ACPs are entered with the same name, i.e. when you create a new list of waypoints in "TheWay". If ACP 1 already existed, and a new ACP called 1 was entered, when the ACP 1 was being entered into the FLPN, the user would have to select which ACP 1 was to be used. There is no way for "TheWay" to see the "new" Waypoint selection screen, so it could get out of sync with DCS and create INPUT ERRORS. This new method also speeds up the creation of a FLPN, as it doesn't have to create the ACPs first. It seems that the underlying CDU systems are working as they should, and it is only the CDU display output that is bugged. So you are still able to create new, and add to existing, ALTN FPLNs. (the display just doesn't follow along when data is entered) The ALTN FPLN summary is still updated, and the route can be shown on the HSD by enabling it. https://github.com/jonsky752/DCSTheWay/releases/tag/v2.5.9 Cheers Jon

You can still tilt them. Their FoV was weird before. The top mirror isn't too bad. The problem is the side mirrors, especially in VR where you likely have to turn your head to see them properly. The pilot's head moves too much, and even with small movements he leans way out into the mirror and blocks the view.

Hi Raven, the team have tested and they are not seeing any issues. could it be a local issue, some strange keybind?

It does, however they've added a switch to the circuit panel on the left side (the bank of fuses in front of of the throttle, the very first switch on the bottom row. Flip it up to enable the system) that turns the system on. After that, injection turns on with the throttle.

I've set my cursor X/Y axis' each with a curvature of 20-30. That slows down cursor movement for small axis movements but keeps the higher speed for larger axis movements.

Nice, I'm using one I found on Etsy, lol. I'd love one that actually matches the real console, tho.

Rudel posted excerpt from manual indicating how it' supposed to work now (?) but I find it even more confusing really

How do you accomplish accurate training without the ability to use the ARK for accurate landing approaches?

Hi av8orDave. Early access can be as long as it needs to be for the module, its a process where we give huge discount to users who then are able to enjoy the module and development process and give feedback that helps development. Some enjoy being part of the process and watching the modules grow to completion and some do not, and I understand early access does not suit everyone. The team are working on tasks and as soon as those tasks are ready they are tested for the patch releases. Patch notes will show the work being completed. thank you

Is there any sort of "guidance" around how long early access is supposed to last for these modules? This was released over a year ago and still doesn't have a functional CDU. Seems kind of, I don't know, wild. Hard to believe someone is working every day on this. I don't mean to be negative, but it might be good to set expectations appropriately.

When I cold start, I always align my HMD. I have set up a vehicle about three miles from the end of the runway so I can boresight my Mavericks prior to takeoff. I use the latest procedure for boresighting. When I reach the target area the maverick is pointing in the vicinity of the target according to the TGP, but it is never actually on the target. I align the maverick manually and press the alignment button again. I fire, hit the target , CABOOMBIE and all that. Select the next target and the Maverick is off again according to the TGP. When using the D type I have the TGP set to AUTO and the Maverick set to PRE. When using the H type I have the TGP set to MAN and the Maverick set to PRE. I understand that the Maverick has to be in range for the AUTO handoff to work on the D type andAUTO handoff does not work on the H type. I'm convinced that the alignment process does not workcorrectly when cold starting. I am using the old targeting pod and D type mavericks. Regards

С внешнего вида воевать можно и на смартфоне. Скачал игрушку в телефон: ни тебе джойстика, ни педалей. И стОит - копейки. А тут - целая наука. Ее познавать необходимо, с нуля... С рисунка Леонардо да Винчи

Hi, I have bumped the report internally, but that is all I can do for now, it just depends on the artists work load. thank you

A note about this livery. It was the original file included with the File 404 Super Hornet model, so this is basically an update of that skin, bringing it into the current mod. The majority of work was his, so I did credit him, but did some tweaks to make it right:

@BIGNEWY Any chance to request high priority?

I've got mine set to 35% for the Y axis saturation for both the X axis RDR cursor and the Y axis RDR cursor. Also, make sure th eTGP is set as SOI. I you have the HUD set as SOI, for example, the crsor will move much fast in the TGP. If anyone else would like to share their settings, I'm always looking to improve mine.

Added a section ref Mods.

+1

Just for data reference, flying low over a burning city in IL2 today, mild stutters and FPS at 65. Just a few seconds of it. GPU (5090) is around 95% useage most of the time (so 0.85 render is spot on), CPU (9800X3D) at 45% (proper heavy assets mission). So it's not 'just a DCS thing'.

whats the frame rate of your monitor? But off the top of my head 70 is an odd number so drop that 60, turn of TAA set textures to high , flat shadow blur off, set clouds to low, chimney smoke to 1... turn off volumetric lights if you have access to discord, submit your dcs log file to the bot on the DCS channel that should help... also note the F-14 cockpit going to have bits of letters missing etc.. thats the way its modelled