brettt777

I think someone, possibly even myself, may have asked this before and if so, I do apologize. I have the Southwest Afghanistan map and the East Afghanistan map. I think I have heard that there will eventually be a North Afghanistan map. Would it do me any good to have the full Afghanistan map at this point? When/if they release a map of the north, if I added that, would it give me any more than the full map?

Okay, my system is struggling with some games, including DCS, but not others. So a couple questions if I may... - Here's my system in a nutshell: Ryzen 5 5900X @ 4.4ghz 64gb DDR4 @ 3200hz RTX3060ti 8gb GDDR5 Rosewil 1K Power Supply OS and all high end games on SSD's I'm thinking the choke point in this system is the RTX3060ti with its 8gb of GDDR5. Two reasons I think this. First, when I upgraded to the Ryzen 5, I ran a bunch of benchmarks before and after to see where I was at. Obviously there was a significant increase from the old CPU to the Ryzen. At first I had the Ryzen at 4ghz on the CPU. So I recorded those and then set the CPU to 4.4ghz like it is now. Virtually no performance increase in any game benchmark. I would think if the CPU was the choke point, there would have been at least a modest performance increase from 4ghz to 4.4ghz. Second, on certain games where my system struggles, I often get a warning about my GPU running out of memory. Kinda weird but I can run a fairly new game like MSFS2024 at reasonable fps on fairly high graphics settings. But when I try to run an older flight sim like P3D V5 (it has VRS Tacpack, so I keep it around) it really struggles like, single digit fps. I recently installed P3D V6 cuz it uses a different engine than the older versions. It runs smoother, but I get the GPU memory warring all the time. So what you guys think? Am I correct? Is my GPU the choke point in my system? Which brings me to my second question. In looking to upgrade said GPU, I'm kinda looking at two new units... an RTX5070ti and an RX 7900 XT/X. On the benchmark site I go to, it shows the 5070ti in the top ten, It shows the RX 7900 XTX a bit lower and the 7900 XT a bit lower than that in the list. But obviously all of them are significantly higher than my poor little 3060ti (It wasn't bad in it's day. A lot of bang for the buck). There are of course, half a dozen or so GPU's that are better than the 5070ti, but I can't afford $2-3,000 for a GPU. A 5070ti is around $8-900 and an RX 7900 XTX is around the same price. The 7900 XT is about $100 less. The 5070ti has the mandatory 16gb of GDDR7. The 7900 XT and XTX have 20 and 24gb of GDDR6 respectively. I have used nVidia GPU's exclusively for years and have always had good performance... at the time I installed it anyway. But I have heard that the drivers for the 5070ti have compatibility issues at times, so that makes me hesitant. Also, I really like the 20 or 24gb of GDDR on the Radeon cards. Even if it is "6" instead of "7". So, what you guys think on this one? 5070ti/16gb GDDR7 or RX7900 XTX/24gb GDDR6? I will also be upgrading my motherboard and RAM soon as well, mostly because I need more SATA ports. I will go from 64gb limited to 3200hz to 128gb at 4000hz +. Unfortunately a CPU upgrade isn't in the budget just yet so I am stuck with the DDR4 cuz that's the only thing Ryzen 9 will use. So, is my GPU the choke point? RTX 5070ti or RX 7900 XTX?

Okay, so y'all will be happy to know that I did NOT give up and I finally managed to get the thing airborne, get the gear and flaps up, and get it trimmed out. Then, of course, I found out that it's actually a very nice airplane to fly. It handles about like you'd ecpect a plane that size to handle but it's also quite fast for a bomber. It will do 300 kts without breathing hard. Anyway, now that I find I can actually fly the thing (with a little help from my friends), I will definitely be adding it to my hanagr. Cheers!

Well, I dunno... but holding the stick back until I was at about 60-70 knots sure seemed to help. I will look for the gear handle lock. Thanks. Maybe there's hope for me and the Mossie yet.

Okay, well one thing I did not know is that pulling the stick back locks the tail wheel. I tried that and I actually managed to get airborne a couple times. But of course, there had to be something else. I could not get my landing gear to go up. The gear handle was moving to the up position but the gear never raised. It never even tried. The first time I thought it was because I waited too long and the higher airspeed damaged the gear somehow. But the second time I managed to get airborne, I put the gear up immediately... at least I tried to. The handle went up but the gear did not. So, is there some trick to getting the gear to raise that I don't know about?

Okay, tried all that. Somehow the thing got set to the simple flight model. The Mosquito must have done that cuz I never use thae simple one. Anyway, all that did was make it worse. It's like, as soon as the tail comes off the ground, the thing just goes out of control and will spin to the left or right and no amount of rudder or differential braking will bring it back. One time out of about 20 attempts, I got it airborne but it was still pretty much unflyable for me and shortly after takeoff it just rolled to the left and crashed regardless of what I tried to make it do.. I don't know what I'm doing wrong but this one is a NO for me. Glad it was a trial and I didn't pay for it yet.

I got the two week trial of this thing and I have yet to get it off the ground. It's all over the runway. I thought the Spitfire was tough to get airborne. This "Mossie" is ridiculous! I have went through every check list and how to that I can find. Prop all the way forward, rudder trim a bit to the right, pitch trim a bit down, roll trim neutral, flaps about 15 degrees, supercharger to "mod". I bring the thottle up slowly and at first, I use taps on the brakes to keep it straight. Most of the time it will just suddenly turn to the right and no amount of left rudder or brake will stop it. And, on the rare occasion that I can actually keep it on the runway long enough to get airborne, I can't get enough speed to even lift the tail off the ground. Last time I did that, I think the ASI was just barely reading 60 knots when I ran out of runway. What am I doing wrong? At this point, I am very glad this is only a trial cuz I would have been major p*ssed off if I would have actually bought this thing. I'd really like to figure this out cuz it's kind of a cool plane, very different... and I would love to get it airborne. So, a couple questions... - Is there some kind of parking brake somewhere that I haven't seen that could be slowing it down? I didn't set one in the controls but who knows? - I have the mixture set to "strong" which I guess means "rich". is this correct? - Are the rest of my setting correct? I thought I saw something in another post about boost. Is there a boost setting somewhere that I'm missing?

The first image is with those added lines in the init.lua file of the Scripts/DSCG/Indicator directory and the init_bake.lua file of the Scripts/DSCG/Indicator/DSCG_Pilot Directory. As you can see, I had a totally usable radar display on the MFD with no adjusting the brightness or contrast. But I also had the overlay. The second image is after removing the lines from the init.lua file of the Scripts/DSCG/Indicator directory. No overlay but MFD is once again a big bright useless blob. Not sure what I was seeing at first when I thought I had a somewhat usable radar display on the MFD without the overlay (with lots of tweaking) but whatever I thought I saw, I guess it was overwritten when I did the last update. Anyway, this is where I'm at now. Whatever textures or functions it is missing for a fully operational radar only on the MFD are obviously added with the other init.lua file. But I don't understand why I'm getting the overlay. I don't understand everything about how these files work to make that determination. It's a bit above my paygrade.

That is what it seems now but when I first did it, I was able to tweak the picture enough to where I could get a somewhat usable picture on my MFD. But then when i went back to it last night and today, all I get is what you see in that image. Not sure what changed.

Okay, so here is a screenshot of the cockpit anf the MFD. For some reason, I can't even tweak it to get a radar display now. This is the best I could get it which, of course, is completely unusable. So, this is what I added to the init_bake.lua file in the DSC/Mods/Aircraft/F-4E/Cockpit/Scripts/DSCG/Indicator/DSCG_Pilot directory. dofile(LockOn_Options.common_script_path.."ViewportHandling.lua") local HUD_onlyRightAligned = true local HUD_onlySz = 0 --8 if HUD_onlyRightAligned then update_screenspace_diplacement(1, false, HUD_onlySz) try_find_assigned_viewport("RIGHT_MFCD") else update_screenspace_diplacement(1, true, HUD_onlySz) try_find_assigned_viewport("LEFT_MFCD") end It's what I found in the radar init.lua file for the F-1 Mirage. I did the same thing for the Viggen and it worked great. Now, at first I put these lines in a lua file called init.lua (along with the aforementioned DSCG_Pilot init_bake.lua file) and I believe it was in the DSCG/Indicator directory. When I did this, the radar display on the MFD worked great, but I had a radar grid overlay on the main cockpit screen. So I removed the lines out of the DSCG/Indicator directory and that got rid of the radar grid overlay but then my MFD picture looked like what you see in the image. I'm not sure what changed but when I first did this a few days ago, as I said before I could tweak the heck out of the cockpit display controls and get a somewhat usable radar picture. For whatever reason, I can't even do that now. The cockpipt display controls have no affect on the MFD picture at all. So apparently what I am seeing on the MFD isn't even a radar picture. I can completely power the radar down and the MFD still looks like that. So, what am I missing here?

I have been able to play around with the brightness and contrast and the gamma and saturation and get a usable display, but it makes the cockpit display unusable. It has to be something with the Heatblur code because I did this exact same mod to the AJS-37 Viggen radar and it worked perfectly.

Well, like I said, I can play around with the brightness and contrast in the cockpit, plus modify the gamma and saturation of the MFD with another mod I have, and I can get it usable (while making the radar display in the cockpit unusable). So it is most definitely the correct display. There's just something else I am missing that needs to be done and it probably won't happen til Heatblur gets around to it.

Actually that's not necessary. I went on the Discord VSN page and found a newer version of thier F-22 and the F-35. I removed the ones I had and tried these and they both worked without a hitch. Ironically, once I saw that these fifth gen fighters had old F-15C cockpits in them, it kind of spoiled it for me. So after all that, it was kind of a let down but hey, live and learn. We're supposed to get a real F-35 some day. We'll see.

Hey, how about this one? I was on board the USS Midway CV-41 in 1980 and we still had two squadrons of F-4J's on board. VF-151 Vigilantes and VF-161 Chargers. In fact, when those Phantoms left the Midway in 1986, they were the very last active F-4 Phantoms in the US Navy. As a US Navy veteran, I have certainly wanted a carrier version of the Phantom in the game. These things were brutal on the flight deck!

I figured out how to export the radar display to an MFD in the Phantom, but for some reason in this plane, it's way too bright and washed out. I have a Winwing 3 MFD setup and most of my modules have one to three displays that can be exported to these MFD's. Three of my modules are not included in the Winwing app to export a display. However, one of those modules, the F-1 Mirage, exports its radar display to one of my MFD's on it's own. The app doesn't even need to be active. Curious as to how this happens, I started asking around to try to figure out how this all works. Then I started looking at various .lua files in the Mirage cockpit/scripts directory. I found a file where it references the viewport handling and then it says to "try to find" this viewport or that viewport. So I went to the other two modules that didn't export... the AJS-37 Viggen and the F-4E, and found some similar init.lua files. I added the lines that talked about trying to find this or that viewport to the same init.lua file that talked about viewport handling, and with a bit of trial and error, I got a completely functional radar display on my MFD for the AJS-37 Viggen. So I tried the same thing with the Phantom. At first, I had the added lines in the wrong init.lua file and all I got was a radar overlay on the main gaming screen. I found a file called init_bake.lua and tried that and then I had radar on an MFD as well as the overlay. Ironically, when I had it like this, the radar display on the MFD seemed somewhat normal. When I removed the lines from the first init.lua file, I got rid of the overlay, but then the radar display on the MFD is totaly bloomed and washed out. I have to tweak the displays controls a bunch in the airplane and then tweak the MFD displays with this other mod I have for that, and I can get the MFD radar display somewhat usable. But then the radar display in the airplane is too dim to see. So my obvious question is how can I adjust the brightness and contrast of the radar display going to the MFD without affecting the radar display in the cockpit? I would think there would be some way to do this but it's beyond me at this point. I figured there had to be some .lua file somewhere to adjust this. Everything else in DCS is controlled by a .lua file. I have heard that the Phantom is not yet set up for exporting displays. I obviously figured out how to do it but maybe there's more to it...? Is some secret file that needs to be tweaked for this to work? The Viggen radar display works great on my MFD. When I adjust the display in the cockpit, the MFD display matches it. So come on Haatblur. What am I missing here? How can I make this radar display on my MFD usable?