Knubinator

Right now it's fun to fly. Whether it's worth your time is up to you. If you want to be primarily air to air, you'll be ok. It needs some work to be good, like some radar modes and a radar gunsight, etc, but the Hornet has the same BVR limitations ATM. If you want to be mostly air to ground or multirole, I would wait at least until we can make/edit waypoints so you can designate your own targets, and we get the cursor zero button so you can find your way home. The biggest holdback to me is the waypoints. I fly mostly AG and multirole missions, so it's important to me to be able to set my own target and IP so I can fly the profile I want to fly. Getting Mavericks and JDAM would be really nice as well. I think it's a really fun plane, and I'm having a great time, but I probably won't be using it in MP any time soon.

I believe it's more for the internal INS system, into which the GPS is embedded. GPS or no, you still need to align that.

Are you using the UFC to change the channel?

Maybe they're bringing back the Radio Maykop easter egg from way back in the day? Because something like that would be just amazing.

This plane was out before NVGs were widely used. So the A/B won't be NVG compatible, but the D might be?

So the indexer is way too dim. The manual says it adjusts 1-14, but in game only goes to 9. And comparing the light in the manual to the game, the one in the manual is way brighter. It's fine for night, but way too dim to see in the day without leaning in all the way or zooming, neither of which are great when you're adjusting trim in the groove. They're all a little too dim, but the AOA Indexer especially is far too dim.

My first attempt was a three wire. I was super long and way right turning into the groove. But I managed to get it sorted and got on course and glide slope in the last quarter mile and caught a very lucky 3.

This is what I figured it all out to be, but it would still be really neat to see the write up on it and how to use it with the RIO to intercept and not necessarily fire on targets. Just nice to see the documentation on it. I'm really excited to see HB expand on the manual, especially since the online version has no restrictions like the PDF has with regards to update schedules.

So my friend and I were in the Tomcat practicing the radar and flying intercepts against another friend in another Tomcat. When he locked up the other plane, I got a bunch of symbology on the HUD and VDI that I didn't recognize. I think I was able to figure out what it all did, but I was hoping there was a guide somewhere that I missed that told me what it all was. To know the actual names and functions behind the symbology. There is somethat's explained in the manual in ther A/A weapons section, but what I'm looking for is all the extra stuff, mainly in the VDI, like the vertical bar, the small T, and the black circle. In hindsight I guess I should have taken a screenshot, but things were moving very fast at 1200kts closure lol.

So I was able to make progress after my last thread, but since this seems like a new issue, I made a new thread. I've made sure all my drivers are up to date, ran memtest to eliminate memory issues, my hardware is in spec for the game, but after the last update, I am totally unable to get into any maps. Before where it was saying not enough memory to allocate sounds (which is funny because task manager shows max 70% RAM usage). Now the error is either Reason: "The GPU device instance has been suspended. Use GetDeviceRemovedReason to determine the appropriate action." Or: "DXGI_ERROR_DEVICE_REMOVED" Which I don't understand, since Nothing has really changed with my computer other than going down to 16GB from 32 due to a bad kit. I'm really hoping I can get some guidance on what to do, since I'm really at a loss as to why I'm having troubles. dcs.log-20190306-212713.zip dcs.log-20190306-211823.zip dcs.log-20190306-211817.zip

So I downloaded the stable branch to test if it was the update or something else, and it seems that it might just be my RAM. I've attached the logs after the CTD while trying to load into a server. Logs.zip

I've attached the log after the last time I had to kill the program after being advised to. It says it can't allocate memory for sound files, would that cause the hangs? I recently went back to 16GB RAM temporarily after finding a bad RAM kit. I'd like to confirm that being an issue before buying more RAM (an issue helps me sell the idea to my wife lol). dcs.zip

I don't know why it's doing this now. Before I believe some of my issues were caused by bad RAM, but that kit has been removed. It gets to the loading screen wit the "init : 75,caucasus.ng5" message and hangs there until I kill the program in task manager. Logs attached. There are only a couple logs from when it crashes itself, but I've had to kill the program a few times on my own. dcs.log-20190302-193432.zip dcs.log-20190302-193714.zip

Is this a view of the back seat? That weathering is so amazing!

Uninstalling and reinstalling the game seems to have fixed the issue? I'll keep playing as normal and update this thread if it becomes an issue again.

Also, running DCS with a pagefile did not help. Still CTD on server connect. Seems it did not generate a crsshlog that time.

I have 32GB RAM on my machine. What would virtual memory give me? I'm just curious if DCS has something about it that page files help.

You should be able to in single player, but you cannot do that in multiplayer. Something about how the game recognizes the player, you have to select your spot on spawn.

Ok, hopped on the acro server for a bit to see if it would stay connected, and got a CTD out of nowhere. As always, log attached. dcs.log-20190110-011707.zip

So I tried the .bak method to isolate the issue, and it seemed to work. So I'm going to input my binds to the new folder, reset my settings, and see if that works for me.

I was able to connect to Burning Skies. I was not able to connect to Blue Flag Caucasus and I tried deleting the shaders as you advised. I had the A-4 mod installed, so I deleted that before trying to be safe. I've attached the crash log from the BF connect attempt. dcs.log-20190109-231936.zip

So I have never had issues with DCS and connecting to servers and missions before, so I'm a bit at a loss of what to do. I tried a repair, update, and can't really think of what else to try. I just reinstalled the game on an SSD, and it was running fine before at least the last beta update. I can load into SP missions just fine so far. When I load into MP, I get the load scren, the map screen, then a black screen when I normally get the slot screen. Then it CTDs on me. Once it crashed hard enough that the black screen never went away and I had to reboot. dcs.log-20190109-020439.zip dcs.log-20190109-021315.zip dcs.log-20190109-021750.zip

It would be normal for them to drop a quick guide to get you a basic understanding of how everything works. Manual usually comes with the module.

Well my hope is that it hits on the 19th or 21st. Less because I want it sooner than later, but I would really like to hear about the Heatblur teams getting Christmas off this year. I feel like they've been busting ass between making the Tomcat come to life and doing awesome work on the Viggen. Honestly, I'd be ok if they announced that they were taking a few days off around Christmas just to have the break. They deserve it, in my opinion.