311Gryphon

Still an issue. I hope it gets fixed. The F4 camera movement SOMETIMES works, and SOMETIMES doesn't with the same setup. It really makes grabbing clips a pain.

Yeah I've read up on the different TWS modes but I'm not seeing any information that makes it clear how to bug additional targets once you're in those modes. I've seen some evidence that it can be automatic but in the official Razbam tutorials Notso seems to manually bug them, and I would assume that's by putting the Acq Symbol over additional targets and hitting the TDC Press...but that doesn't really seem to work for me. I can get into a variety of TWS modes I just can't reliably get multiple targets bugged, so it's getting a little frustrating. I'm 90% sure it's because I'm misunderstanding the process or doing something wrong. I'd just like to know how to get the targets bugged once I'm in the preferred TWS mode.

I've had some mixed results since I posted here. Sometimes it does automatically bug other targets and sometimes it doesn't. I thought their was a way to toggle that function but I've never actually switched anything up so I don't know.

Compared to the Viper it's a dream. Also, isn't the NWS ALWAYS on? The NWS button is for High Gain. Or is there a way to turn it off completely? If so, I've never used it. But anyway, I find that the Viper is a bit easier to get to the surface gently but the Strike Eagle is much easier to get to a stop, in a straight line, once I've touched the pavement.

I'm apparently unclear on how to get secondary targets in TWS in the Strike Eagle. I assumed after you get a PDT and then enter one of the TWS sub modes you would put the Acq Symbol over a secondary track and TDC Press on that to designate it SDT. I do that and nothing happens. I can only bug one target no matter what. I've tried this in a few different scenarios and have even remapped my TDC Press to other controls. Nothing. I can't bug more than 1 guy. Is it a different button that designates subsequent targets?

I've done several missions where I've successfully gone from RBM to a good HRM Map and it seemed to work as it should, and as shown in several of the videos I've watched. Today I jumped in a mission and have tried several times to get a good Map but after activating the Map Cursor Function the timer starts to count down, but stops after a 2 or 3 seconds and won't continue. I'm curious if anyone else has run into that issue, or if anyone knows if it's just something I'm doing wrong. Here are the specific things I've done so far. Put Target point within a few hundred meters of my target Flew with Target Point about 35° off my port side, straight and level Took Command of A/G RADAR as pilot Set Cursor Function to MAP Slewed a 4.7 (I think) box over the Target Point Ensured it was not disabled (X-ed out) TDC Press to activate Cursor Function Scope went to the HRM and map counter started counting down Stopped after 2 seconds I reset to RBM Scope and tried again with same results I reset to RBM, changed my angle to be closer to 25° and tried again with same results Same but at an angle closer to 40° with same results Same tests but closer Same test from WSO seat It may just be this mission or the mission location or something, but there should be plenty of contrast at this location. And now that I think about it, my RBM scans are trash. That doesn't seem to be working as it should. Flying along the ocean with a relatively flat desert seems like it should at least show a clear delineation between the ocean and land, and it does on the first sweep. After that the scope just fades to black and subsequent sweeps do nothing. I've tried to adjust brightness and contrast. I'm not sure if that's related though because I had that happen on a mission last night where I was able to get good HRM Maps.

Another livery/skinning question. I've changed my pilot body, details, and the helmet shell. They look perfect from the external view and if I'm looking in one of the mirrors. But if I'm pilot looking forward at my CP/G, or if I'm CP/G looking back at my pilot, the textures are default. I'm wondering if there is a way to fix that. I've downloaded several other skins that have helmets or patches just to test it out, and they all do the same thing. I have also dug through the default textures, and exported a default description.lua from Model Viewer. I don't find anything in there that gives me any leads. I did find some lines in a description.lua file somewhere that looked to use different material names so I tried those to no avail. My guess, at the moment, is that there's just no way to define these right now and that's hardcoded or something of the sort. Either that or it's just a pain so nobody is bothering. It's not the end of the world since generally you won't be looking backwards at your pilot's face, but since I'm going to all the trouble I'd like to have it right. If anyone has any help that would be great. Thanks.

There has been talk of GIMP supporting .psb and I found a plugin that was supposed to work, but for whatever reason it did not with these files. The link from the other forum that I pasted up above was for some converted .psd files that someone made. They just downsized them, which works fine for our purposes.

I don't own the inside either. LOL. Anyway, thanks.

Here is a link to some converted files from another thread. These are converted and will open in GIMP.

Anyone know where these can be found? I'm either missing them or they aren't located in the CoreMods>aircraft>AH-64D>Textures>AH-64D.zip. The .zip has pilot files and external cockpit files but I'm not finding any internal ones. I've been searching Google and this forum for an hour or so and can't find any hints. Thanks!

I've had many, many, many tracks that didn't play properly despite me not putting any new inputs into them, so just loading the track and watching it without flying or hitting any keys doesn't necessarily work. It's actually quite frequent that your plane will still plow into the ground. The following are things that I find to be quite broken almost all the time: Tomcat (every track I've ever played is extremely broken) Carrier landings (your plane will not be aligned with the carrier and will "land" in the ocean) A-10C II (any time you use the TGP it will wind up being miles away from where you actually set a SPI and that seems to confuse the sim and send your plane flying to the wrong locations, also any weapon you employed using the SPI are going to miss by miles) Dogfights seem to be about 50/50 (your plane will wind up following nothing or being in the wrong place so the enemy that you killed doesn't die and will eventually launch missiles that were never launched at you and you will die) These things aren't necessarily ALWAYS broken (except the Tomcat and A-10C TGP stuff) but they get quite frustrating. Anyway, my initial point is that just replaying the track doesn't necessarily result in a clean replay. At least all of this has been my experience, added to the pile. Thanks.

About a month ago a started a contest with the upload of my DCS mini-movie. I finally got around to announcing the winner in case anyone was curious. Spoiler though, if you haven't gotten an e-mail from me yet you didn't win. Sorry!

Here is the actual mini-movie. Contest link is in that description as well if you need it.

Not sure where else to post this but I wanted to spread the word, and this looked like as good a place as any. This video is just the trailer for my video coming out next week, and an introduction to the give away which will go live when the other video does (midnight, central time, July 23, 2021). It runs till August 20th. Enjoy and good luck!