

rob10
Members-
Posts
3333 -
Joined
-
Last visited
-
Days Won
1
Content Type
Profiles
Forums
Events
Everything posted by rob10
-
With 16 GB of RAM you need a bigger pagefile than 16 GB. Sure maybe it ran fine before the update, but you were likely on the edge of issues but hadn't quite gone over. New stuff was added that pushed you over the edge and now it's not working. FROM YOUR LOG: 2025-03-17 19:13:52.539 ERROR BACKENDCOMMON (6944): Can't load image './Mods/aircraft/Mi-24P/Cockpit/Scripts/../IndicationTextures/ASP17_flex_sight.tga'. Reason: Not enough memory resources are available to complete this operation. 2025-03-17 19:13:55.540 ERROR EDCORE (14144): More out of memory in ed_malloc for 1229984 bytes.
-
Thanks. I wondered if it was a "normal" Viggen thing. Flagged it since it was repeating at the end of the log so seemed like it might have been an issue. Glad to have a real answer on it!
-
More knowledgeable people than me may spot something that I didn't, but no big red flags I saw. I'd start with temporarily removing your Mig-21 and A-4 mods. Mods have been known to cause issues that wouldn't seem like they should be related (i.e. supercarrier wouldn't spawn after one update with a particular plane mod installed). There is also this repeating at the end of the log which I can't recall seeing before: 2025-03-19 23:04:06.916 INFO VIGGEN (19436): Custom cartridge file found! C 2025-03-19 23:04:06.916 INFO VIGGEN (19436): FOLDERID_SavedGames: C
-
Your anti-virus is deleting files. Look around the forums and you'll find lots of reports/solutions.
-
Post your log file. You'll find your most recent one in your DCS Saved games/logs folder. If you have file extensions hidden it will be dcs, but likely it will be dcs.log For the record, DCS has only had multi-thread option for some time now (single thread was depreciated), so that's not going to factor into the issue.
-
Authorization failed after DCS 2.9.14.8222 update
rob10 replied to DeNbEiRe_BE's topic in Installation Problems
There is a little box in the top right corner of this thread with "search" in it. Type "authorization" and hit enter. There have been probably 20 new threads started about this (or what is virtually the same) issue in the last 2 weeks. Short answer is It's your antivirus causing issues. -
Taxi/Takeoff training mission - CAN'T remove chocks
rob10 replied to rob10's topic in Bugs and Problems
Thanks @BIGNEWY, never thought to try resaving, but that seemed to update things and it worked fine after I did that. -
resolved Taxi/Takeoff training mission - CAN'T remove chocks
rob10 posted a topic in Bugs and Problems
Mission was built before chocks were available (it mentions that fact) but since they are now available they are applied. And you CAN NOT call the ground crew (tried bound button and default keybind, menu won't come up) to remove them (and no keybind to remove them) so you can't do the taxi part of the mission. -
Your anti-virus is blocking the F-14 files. Very common issue currently. Check the forums and there are all kinds of post explaining how to fix.
-
They are telling you that the unit is beyond limits side to side (6 degrees rather than max 5 degrees) but within limits front to back (1 degree vs max 5 degrees). So you need to place it on leveller ground for it to be able to be functional.
-
No apparent reason for it, but NordVPN seems to be coming up as a problem with number of people in the last week or so. Likely something that would need to be tweaked or fixed on their end.
-
F14 not authorized / antivirus / false positive
rob10 replied to Semaphore's topic in Bugs and Problems
It's your anti-virus. There are lots of threads about this issue and how to fix it if you search around even a little bit. -
FA18GPS the issue of the coordinates of the guided bomb
rob10 replied to Qazplm's topic in Bugs and Problems
From your other post, you're flying the F-18 as a RED COALITION member. Unless you have Unrestricted SATNAV selected you're going to have a degraded GPS so no wonder it's not hitting accurately. This is a prime example of why we ask for a track file when trying to help people. It's usually the little details that they don't think to mention because it doesn't seem important to them that are the root of the problem. -
See this reply from further up the page: And add a track if you want to get actual answers about your specific case.
-
Do you have them plugged into a USB hub? Is it powered? My 1st thought would be not enough power. Try swapping the bezel that not showing for one of the ones that is and see if it's working. That should rule out hardware (cable or physical device).
-
Yes, DLSS isn't a good option if you have a higher end system. You can't get something for nothing so the tradeoff is some ghosting or less clarity in return for higher FPS and potentially higher resolution settings. For people flying in VR a lot of them are happy with the tradeoffs. DLAA can be turned on independently of DLSS. DLSS does not need to be activated to have DLAA turned on.
-
Completely guessing what your problem is, but you need to turn the external lights either off or on (can't remember which) for the Tomcat if I'm not mistaken (rather than saluting like you would in the Hornet).
-
In iron bombing CCIP mode, Hud still shows AUTO
rob10 replied to Gunner4968's topic in Bugs and Problems
You have unlimited ammo/weapons checked on in your settings. -
can not reproduce Cant fire any Weapons in the f18
rob10 replied to SOLIDKREATE's topic in Bugs and Problems
At 300 kts you very probably broke the gear doors (250 kts is max deployment speed) which will inhibit weapon release. As I said before, maybe not enough to damage the gear itself, but if you damage the doors you can't fire weapons. This used to be a common issue when people weren't retracting gear fast enough coming off the boat. -
Moza inconsistent information about supported grips
rob10 replied to trev5150's topic in Input Devices
If they told you it worked but it didn't, then maybe I could see the point of your post. But them telling you it won't work but it does? Pretty hard to get upset about that. Saying it DOESN'T work I imagine would be the default position if for some reason someone wasn't sure of an answer but was answering it anyway because there's a lot less chance of blowback if they say it doesn't work but it actually does. In fairness, it's arguably in their own interest to "officially" claim it doesn't work since maybe that'll drive more people to buy their stick and base rather than just a base. I can't really fault them for that either because any indication of support and you'll be back screaming that they won't help you with their competitors hardware. I agree with previous posts, either there's a language issue or else you're making a mountain out of a mole hill. -
If you made it up to FL18 with gear still down you likely went fast enough to rip the gear doors off, so even though you could technically retract the gear, the F-18 systems would have considered that serious damage that would prevent weapon employment.
-
The Ocasional FPS Drops In Full Fidelity Aircraft
rob10 replied to FierceLV's topic in Game Performance Bugs
You may not realize it, but you are on the current version of DCS so you ARE using the MT version (from your log: DCS/2.9.13.6818 (x86_64; MT; Windows NT 10.0.19045) since there is no ST version anymore. That's not really important to your question though. Taking a quick look at your log you should set your pagefile to 32GB set max and min value, set it on your fastest drive, and make sure that drive has at least 10% free space (after taking the 32 GB for the pagefile into account). You've only got 32GB RAM and your pagefile is showing about 4GB so you're almost for sure running out of memory with full fidelity planes. -
If you have PRIORITY (i.e. the little diamond in the top right of the MFD) on SA page, it will perform the EXP (expand) function the SA page. It will blank the HMD if you have priority on the HUD or any MFD that DOES NOT have the SA page on it. Not a bug. And if it's not that, remove any mods and do a repair and if it's still happening post a track because it's working fine for me.