II.JG1_Vonrd

Single player mission launched from Mission Editor. Hot start from ramp. 30% fuel. Nearly constant Fuel Cautions. Track attached. Caution Aux Fuell.trk Understood. Thanks.

Seems like this might be related to my having difficulty achieving a steady hover. Pretty difficult to get external cargo hooked and delivered. Sure, practice will help but compared to the Hip I find the Chinook more difficult.

Same here. I also have constant EAPSI FAIL indications, as seen in the photo above, even after selecting all EAPSI switches on.

Not sure that it will help but check "Full Screen" checkbox

I had the same issue with low FPS since this latest update and it translated into other modules, especially helicopters. It was apparent that the game was struggling to load shaders. After looking at what had changed, I noticed that "Full Screen" had somehow become un-checked. I tried to re-check it through the loading screen without result. I then did it through Skatezilla's GUI and it worked. I now have high 20s in FPS for the CH-47 and it is flyable but other modules have high 40s FPS. It's early access... Devs, any files that I can upload in order to help troubleshoot? For the record here's my PC specs. CPU - AMD Ryzen 5 7600X MOBO - Gigabyte B650 Aorus Elite AX Memory - G.Skill DDR5-6000 (4 ea 16Gb. Total 64 Gb) P/N: F5-6000J3238F16G-fx5 Graphics card - PNY GeForce RTX 4080 Storage - 2 each 2TB P3 NVMe PCIe 3.0 M.2 Internal SSD VR - Pimax Crystal using OpenXR latest build OS - Mindows 11 Pro 64 bit EDIT: Looking at posts above, it seems that there is an overload in the textures dept. of the Chinook. I don't need eye candy as much as I need playability. I understand that it's a constant balancing act. I don't have an Uber machine but it's not shabby. What about all of the others with lesser specs? Bad business to force them to turn all settings to the bottom just for eye candy's sake.

I humbly disagree. From most historical pilot reports and from my RL experience as a PvtP, the way to ID distant bogies is to have your eyes focused on infinity and scan by quarters. More often than not you will see something in your peripheral vision "out of the corner of your eye" and are then able to focus your gaze. The suggested varying of dot size by being larger when not being directly looked at is interesting. Not sure if it's doable in the game though. I also would really like to see sun glints incorporated. The old IL2, as I recall, had this feature and would be realistic from my RL experience. As for how spotting is post update... I'm glad the Blob is gone. I don't spot at long distance as well as I did with the Blob but mid range is fine. The only issue I have is that some of my squad (mostly with Quest versions of VR) see bogies well before I do. I'm Pimax Crystal Sim with settings to maximize clarity and graphics. Yes, I know that dumbing it down will increase the apparent pixel size, but why spend big bucks and not take advantage of what it has to offer graphicly?

Not really a bug but I'm not sure where to post this. Please move to proper section if needed. I really like the feature of being able to copy coordinates from the F10 map using LAlt+LMB but could you make it also a button bindable action? Many VR users have difficulty using the keyboard. Also, I can't figure out out how to make it a VoiceAttack command since I don't see how to have the LMB as part of a command.

Using mini stick on either my Virpil throttle or Winwing joystick, I just can't get a happy medium between too fast or too slow. Tried curves, user curves, and saturation (y-axis). Greatly reduced Y-axis saturation in combination with curves has worked best but, to get slow / fine adjustment, I have to give up enough speed that it takes too long to move, say 45deg. I have the same issues to various degrees in other modules. I wish there was something in Specials or General to have better control.

Ah... thank you! I was equating the arg numbers with the line numbers in the left column of the lua. Duh...

@Zabuzard Not to belabor the issue but I notice that the draw_args lua doesn't really relate to what actually works in the Model Viewer. For example, lines 9 & 10 operate the flaps in the MV but in draw_args 9 is "LG_Lever = 5," and 10 is "Toebrake_L = 6,". In fact, most of the args that work in MV don't relate to draw_args. This means (unfortunately) that Livery makers are back to moving each slider in order to see what works in the Model Viewer. It's beneficial to be able to drop the flaps, gear, slats, etc. in order to see the areas of the skin that are hidden when they're up / retracted. Is there somewhere a lua that lists the args that work in the MV?

This skin continues the lifespan of Phantom II F-4E-60-MC, S/N: 74-0644 last seen at Seymore Johnson AFB NC when it was with the 335th TFS (”Chiefs”), 4th TFW. It went through aerial target conversion to a QF-4E drone, No. AF262 by BAE Systems at Mojave CA in June 1991. It was operated and maintained by the 82d Aerial Targets Squadron at Tyndall AFB FL. It's final day is listed as "Expended 09-NOV-07". Submitted to User Files 7/18/24

Here: C:\Program Files\Eagle Dynamics\DCS World OpenBeta\Mods\aircraft\F-4E\Cockpit draw_args.lua. Actually, there is also a draw_args.lua in the F-14. As far as I know, these are the only two modules that have a draw_args.lua. Would the list of arguments for other modules be available under a different file name? It would be helpful if they were. Going through the multitude of sliders in the ARGS tab in the Model Viewer is quite tedious.

If anyone's interested I've compiled the ARGs for the F-4E (by fiddling with the sliders in MV). It's by no means comprehensive. I wish that ED and module makers would provide a full list of ARGs for each module. So, a question... I want to make a QF-4 Drone skin and want to have it launch in game as NOLO (no pilot and WSO). If I included the ARGs that remove them (50 & 701) in the description lua, would that work if it's designated AI in the Mission Editor? What about if it's designated as a Player or Client in the Mission Editor? ARGs.ods ARGs.pdf

This skin depicts F-4E-60-MC, S/N: 74-0644 of the 335th TFS (”Chiefs”), 4th TFW Pilot Lt. Col. Richard B. Myers at Seymore Johnson AFB, NC circa 1982. A few things of note in this skin: The rendering of the "4th Tactical Fighter Wing" badge. As I understand, the badge emblems were water slide decals (like a plastic model) which were protected by a spray clearcoat. These would eventually breeak down and flake off around the edges. The gloss, overspray and chipping were rendered to replicate the photo as best that I could. The dark fuzzy border of the dark green. I don't know but theorize that the field of the color was applied using masks and then outlined with the spraygun set to no fan (airbrush) to soften the edges. The paint mix used might have been slightly darker. Or maybe it's due to the reflectivity in the thin overspray edges. I've seen similar when I used to paint aircraft. Shoulder patches for the crew's uniforms. Custom helmets with the Pilot's and WSO's handles. Totally surmised by me. I could find no references. Thanks to: @MagicaThunder for his "Homemade Paintkit" @MigMaster for providing the correct default colors per @ben_der. @ben_der for providing the F-4E Wireframes. Submitted to User Files 7/12/24. Awaiting approval.

Are the colors really as dark as shown in this image? Several photos of this aircraft / squadron are the same. What about this 4 view? This seems more likely to me (but I actually kinda like the dark colors).

IMHO, I consider myself to be a fairly competent skinner at this point. I would really like to advance to the level of skinning modules in early development and supplying "default" skins. I'm not sure as to how to proceed in this endeavor. Anyone who is on an "official" skinning team, how did you go about getting there? I'm retired and have pretty much unlimited time available. I'm well versed in the software needed... Photoshop (of course) Substance Painter, Blender (I would consider subscribing to 3dsMax but that's a pricey bit of kit ). Anyway, any advice would be appreciated.

@Bazz_Mulder It seems that your request will be fulfilled by the HB skinning team.

In that case should I not make a livery? I don't want to step on any toes.

No. If you set the acft on the map as "Start at Parking" (I think that's it... whatever in parking and cold is) the start cart will be there.

Alright... revision of the helmet complete and has been updated in User Files. Here's the link: https://www.digitalcombatsimulator.com/en/files/3339337/. I based the colors on the helmet located at the USAF Museum in Dayton, OH. The markings I based on what is claimed to be an original helmet of Maj. William L. Kirk, a close friend of and squadron mate of Col. Olds. Here's the link to his story: yankeeairpirates.overblog.com/2017/10/maj.william-l.kirk-433rd-tfs-mig-killer.html I could find no images of Col. Olds' helmet with just the two kill markings and decided to use Maj. Kirk's as reference. I would think that Olds' first two kills should probably have MiG-17 silhouettes but without evidence decided to go with Fishbeds. The colors are the best match that I could get given that colors appear different in different lighting, in game and on different monitors / VR. Phew...

Yeah, I found photos of the USAF Museum helmet and uniform. I'm going to try and match the colors as well as I can given how color rendering changes due to lighting conditions. That helmet is the 100 mission version showing 4 kills. I'm going to render it as 2 kills in keeping with the time line of this skin. I'd really like to see the helmet that your team has done.

I have heard that the colors that I used on Col. Olds' helmet are incorrect and that the dark brown should actually be Olive Green. Would the photo showing the rear view of the helmet be more correct? Does anyone have some other photographic evidence? I'll try changing the colors and post them to poll what y'all consider best. Thanks I'd be willing to give it a go. Do you have any more images of that particular aircraft? S/N 74-644.

This livery is a depiction of (then) Col. Robin Olds' F-4C-24-MC Phantom II, S/N: 64-0829 after achieving two VPAF MiG-17 kills which occurred on May 20, 1967 with his Weapons System Officer 1st Lieutenant Stephen B. Croker. (Lt. Croker is identified in several historical documents as Col. Olds' WSO. I could find no reference to "I LT LAFERTY" who is depicted on the nose art). I've attempted to render this livery to be as close as possible to the famous photo showing Col. Olds in his Boony hat in front of SCAT XXVII including the wearing of the paint. I did have to take some license in the placement of the nose markings since the F-4C has a shorter nose than the F-4E and no gun. Included also is Col. Olds' helmet (again derived from a famous photograph). I believe the photo depicts his 100 mission helmet and would show more kill markings on the back than his two kills at this time. I found a replica helmet which shows only two kill markings and used that as reference. I also made a fictional helmet for Lt. Croker based on some examples related to the period. The included images have been Photoshopped as attempt to match the historical photographs. A big thanks to MagicaThunder for his "Homemade Paintkit". Link: https://www.digitalcombatsimulator.com/en/files/3338228/ If you don't know about Robin Olds who retired in 1973 as a Brigadier General and died June 14, 2007, you really should learn about this S/H fighter pilot. Wickipedia is a good place to start: https://en.wikipedia.org/wiki/Robin_Olds Submitted to DCS User Files 7/2/2024. Awaiting approval.

Bind the same controls that you have for Visor and Sunglasses in the F4E-WSO controls section. Jump in the WSO seat and set the Visor / Sunglasses the way you want them then jump back in the Pilot seat. I think they will stay where you set them.

I'm almost done with a Livery for Robin Olds' SCAT XXVII and part of it is a flight helmet for Col. Olds. I wanted to replicate the famous photo of him in the cockpit. I couldn't figure out how to remove the O2 mask while in the game so I had to do a bit of Photoshop. I'm pretty pleased with the result. The full Livery will be posted very soon.