XCNuse

GOTCHA, okay, I'll try that tonight; I didn't see anything that points that out; and obviously it didn't prompt me so wasn't sure what I was doing wrong. I've come to the conclusion what I really need is something to hold my tablet in a reasonable place lol, that is what I was fighting with more than anything else last night haha. Fun app! Also not a big fan of the swipe to change screens; on some things I want to swipe or end up swiping on things like the dobber switch on the Viper, and obviously it's tossing me to other screens I don't want to use. I think I had more issues with said dobber switch than anything else, I can't tell if the "click spots" are too small by comparison to the other buttons/switches or what, but it was tough to get it to work in a way I was expecting.

I don't own the Hornet, nor the Supercarrier, nor have interest in spending the kind of money involved in this campaign, but will the soundtrack be available for separate purchase? edit- (if that read wrong, what I mean is) : if I owned the hornet I would be all over this, but the investment of the modules just to have the campaign means I'll likely never get to buy it, but have interest in the soundtrack.

So I've got it installed and set up the config and everything seems to check out... except.... MFD buttons don't seem to do anything. Interestingly they aren't glowing green like other buttons when I touch them as well. Was able to control the UFC and everything in both harrier and F16 with the displays outputting, but for some apparent reason, the MFD screen doesn't work. Tried again with A10Cii and no dice, MFDs on my tablet don't seem to react; interestingly after a while sometimes I'll even get "kicked" out of them and back to the program's main screen. edit - FYI I don't mean visually, I realize not to currently expect a "video feed" of the displays, I mean.... nothing... works, on the MFD page, no button response of any sort; but all other pages do work, and displays (like CDU and DED) output just fine.

Fantastic, thanks guys! I'm excited to check it out tonight on a mission!

Just ran into this from someone on the DCS Discord; but am cautious, as I am an iOS user, but have a single Android tablet; technically an Amazon Fire HD8, but it's the first generation HD8. How intensive of an app is this thing? I believe my HD8 tablet's specs are: Arm A7 2x@1.2ghz, 32bit, 1gbram I have no idea what any of that means on something like a tablet; I know it's slow (it's now 6 years old and wasn't fast back then), but does anyone know if something that slow would be reasonably acceptable?

As an update, set up a very similar trigger setup as yours in those screenshots Rudel, thanks for that, works PERFECTLY!

Must be a time multiply issue; Thanks for that Rudel, I like that method better than what I was doing by increasing the flag! That said I think I could do some interesting things with a +1 to the flag with random events and random flag counting, but I'll check out that method instead!

very strange.. Mind doing a test for me then, if you go into a speed multiply mode; does it lose track then? I think it's ctrl-z? or ctrl shift z? the repetitive trigger should have a pop up "test" every 15 seconds but, the first one for me was at 16 seconds mission time (as expected), the second one was ~32+ seconds, the third was around 47 seconds, and the fourth was at like 70+ seconds or thereabouts... I'm not 100% positive if I didn't test it without time multiplication, was running tight on time this AM, but surely time multiply shouldn't break a time counter like that that fast either way

Tried to use time since flag as a timer to keep track of the time to spawn in units, was doing a quick test having it run every 15 seconds and spitting out a message to check it. I noticed that within even 1 minute, the timer had fallen off track time-wise very quickly, surely something is wrong here. Alternatively, anyone reading this, if you have any solutions that would increase flag value every X minutes, would be appreciated! time since flag not keeping track of time.miz

Kiowa now sounds like it's going to be set way off in the distance of 2021, IF even 2021. But PC's expectations on release now seem incredibly relaxed and back to "it gets here when it gets here," and there's still a lot to get done. But, without raising eyebrows it seems like multicrew is a bigger possibility now, and no longer a "not going to happen."

So returning to this once again, I just timed it. for reference, 6700K @ 4.4Ghz, with DCS on an NVME over PCIe. NVME as tested on CrystalDisk; Sequential read at 3400MB/s and write at 990MB/s, 4Kib Q8T8 at 801/811; so it's... plenty fast; Timing: 1 minute, 20 seconds to go from splash screen to the main menu. CPU sitting at 1% that entire time on DCS.exe, never climbed to 2% until the screen blacks out from the small splash screen. Windows Defender however sitting there DESTROYING one of my cores in the meanwhile... So it was Defender the whole time. Added an exclusion for DCS, and now it starts up in 20 seconds. For anyone looking for an answer; start up task manager and watch for Windows Defender, because that may be the issue. Edit - For what it's worth "well that's obvious," I had done this previously actually a while ago, and upon shifting DCS from a SATA SSD to the PCIe NVME, I forgot to include that rule as well; which is roughly in line with 2.5.6 update, and why it was such a problem for me. And the other reason I never really caught it is while looking at Task Manager, the CPU use appeared low because Defender was only running a single core / thread process; meaning what I saw graph wise in Task Manager was... well not very obvious until looking at the exe's themselves.

on an NVME drive over PCIe, so about as fast there as I can get. I'm curious if the 4 core of the 6700K is the issue for me.

Yeah I have it enabled but; it can be me being shot at and the frame drops are equally as bad, it seems to not matter what gets hit, if it's anywhere around my computer comes to a complete stall for each hit. It's kept me from checking out multiplayer because I assumed it was just as bad.

I just bought a few WWII modules to get into it, only to realize I guess my setup can't handle it. (6700K, 32gb 4000mhz ram, 1080Ti.. specs are far from being a slouch) even on an empty mission except myself against say a B17 if anyone takes any amount of damage I lose all frames; it returns, but each individual hit, my FPS drops to 0 for half a second or more at times. I don't understand what it is though; watching a Growling Sidewinder video and he has zero issues. Watched a video from Nineline more recently and he had no issues; but his older tests he'd get the massive stutters as well. I don't get it, but it's absolutely unplayable in its current state for me, beyond just flying around.

yes lol I'm fully aware how the module functions, I'll have to continue testing to figure out what caused it. Has anyone else tried zooming in, and then switching to IR?

I very much imagine it was; but if that were the case, then the TV (non-IR) should've appeared black, however it was not; it ended up being white, and... a brighter white. I haven't had a moment to attempt replication but, I'm holding onto the zoom being the culprit over the warmup time. I know it wouldn't have been down to full warmup time as that flight was more than 10 minutes long and being at night I switched the IR on after startup, and had used the camera itself for certainly more than 3 minutes and not being able to figure out how to make it not white I had to give up the flight. So I'm not sure, but I know it wasn't down to warmup time, UNLESS, it doesn't function properly after trying to use it before it cools down, but I'm pretty sure that's not the case. I'll have to play with it more to figure out what happened and what I can do to make it happen again. I'm still partially curious about that last flight where it happened, and zooming out fixed the issue, BUT, that was a quick test, and was more likely to be in the warmup timeframe.

Interesting idea, it's a high possibility, I'd have to look at the default binds then. I don't think so, but I'm not sure. Unless I run into whatever that issue was again.

This is what I'm now under the impression of it being.... And it makes complete sense too for training; it's modern enough, allows for transitional pilots from the F/A-18C. It just makes sense.

As a follow up, I have not been able to make this happen again. Still no clue why it wouldn't work that first flight, but so be it.

Interesting... I wonder if that goes under my list of the same issue I had with the litening in the A10C2 last night; couldn't lase, turned it off and back on and apparently I could lase again. Will continue to fiddle with when I have a chance, will produce a track if need be. Seems odd it happened to two of us in three different aircraft.

Wait... you can remove the HUD camera??? How?

I just went into the keybinds menu, load config, went to the 14B input folder and had it load in the controls that way; didn't have to copy and paste anything. Only odd thing it didn't transfer was toe brakes which was a bit strange, but that was it, all other axis and inputs transferred.

Trim no longer works after today's patch. Even clicking the trim buttons on the stick in-game ensuring no double binds or anything... no trim. Can anyone else confirm this? Two ship with a friend and I were not able to trim on a multiplayer server just now.

Nothing has changed; and reason this is a big deal right now is not being able to fire laser for APKWS or other manual reasons. It was working before the patch, which is why I bring this up. No double binds.. edit- Interesting... very... interesting. Shut off the TGP again, along with safing the laser. Turned it back on... now it's working??? seems odd.

With today's update came latch enabled by default however NWS which is listed as the only way to fire the laser no longer... fires the laser. Anyone else having better luck? Yes obviously laser is on and armed.