@jip As implied, the unit is originally from the BlackOps line of mods. Yes, it is the Citadel MK II.

The unitpack, I'm talking about where I noticed the issue from, is Mixed Combat Pack (MCP): https://github.com/SmalkiGroove/mcp-mod . MCP mixes together popular units, of various untipacks, and bugfixes/rebalances them together for one mod (TotalMayhem is notorious for having more powerful units vs. vanilla). My main interest in the mod is the backbone programming work he did, and notsomuch it being a convenient unitpack in one mod.

I did check over the BP file of his version of the Citadel, and it's fine. Here's a Winmerge report showing the differences: Citidel differences.7z . The left column is basically Uveso's BO release, and the right column is from MCP. The differences are just unit stats, and sourcing to make the unit work in his mod. And yes, I did follow-up on the Railgun01 files, and didn't see any differences there over Uveso's BO release.

I also mentioned running my standard mod array testing this (this doesn't include MCP - I only recently discovered it this past week). I ran a sandbox game, and this is where the screenshot came from. All those projectiles are "stuck".

I will see if any of my other mods are interfering with this, but I'm raising doubts. When I ran MCP, for my LAN session, the only other stuff running was basically QOL stuff. This seems to be something caused by the recent patches. I don't recall seeing this issue, beforehand, with the Citadel.

@uveso I'm not sure what you guys did in recent patches (3721+), but any unit using the Railgun01 projectile is borked. The particle effect won't go away, and it builds up in the sim, and lags the whole game. My last LAN game had the Citadel in it (via MCP, but I confirmed the problem on regular BlackOps game, too), and I had to constantly run the "Purge Projectiles" command in any attempt to try to finish the game.

Do you know of any short workaround outside of the obvious (banning units, etc)?

I've only ever used my current username. What you read is the system name (which I do it after my mobo). This is a Asus B550 Strix. I can't explain the error since the game ran fine before, and it broke while trying to install the last update. As I stated, uninstall, clearing caches/config files seem to do nothing. Is there a client config I'm missing somewhere?

I've already deleted, and did fresh installs of everything (including doing a new game profile). I keep getting the annoying error:

Jan 29, 2023 5:30:40 PM com.sun.javafx.application.PlatformImpl startup
WARNING: Unsupported JavaFX configuration: classes were loaded from 'unnamed module @4ee26bae'
Logging system failed to initialize using configuration from 'classpath:logback-spring.xml'
java.lang.IllegalStateException: Could not initialize Logback logging from classpath:logback-spring.xml
at org.springframework.boot.logging.logback.LogbackLoggingSystem.loadConfiguration(LogbackLoggingSystem.java:242)
at org.springframework.boot.logging.AbstractLoggingSystem.initializeWithSpecificConfig(AbstractLoggingSystem.java:66)
at org.springframework.boot.logging.AbstractLoggingSystem.initialize(AbstractLoggingSystem.java:57)
at org.springframework.boot.logging.logback.LogbackLoggingSystem.initialize(LogbackLoggingSystem.java:188)
at org.springframework.boot.context.logging.LoggingApplicationListener.initializeSystem(LoggingApplicationListener.java:335)
at org.springframework.boot.context.logging.LoggingApplicationListener.initialize(LoggingApplicationListener.java:298)
at org.springframework.boot.context.logging.LoggingApplicationListener.onApplicationEnvironmentPreparedEvent(LoggingApplicationListener.java:246)
at org.springframework.boot.context.logging.LoggingApplicationListener.onApplicationEvent(LoggingApplicationListener.java:223)
at org.springframework.context.event.SimpleApplicationEventMulticaster.doInvokeListener(SimpleApplicationEventMulticaster.java:176)
at org.springframework.context.event.SimpleApplicationEventMulticaster.invokeListener(SimpleApplicationEventMulticaster.java:169)
at org.springframework.context.event.SimpleApplicationEventMulticaster.multicastEvent(SimpleApplicationEventMulticaster.java:143)
at org.springframework.context.event.SimpleApplicationEventMulticaster.multicastEvent(SimpleApplicationEventMulticaster.java:131)
at org.springframework.boot.context.event.EventPublishingRunListener.multicastInitialEvent(EventPublishingRunListener.java:136)
at org.springframework.boot.context.event.EventPublishingRunListener.environmentPrepared(EventPublishingRunListener.java:81)
at org.springframework.boot.SpringApplicationRunListeners.lambda$environmentPrepared$2(SpringApplicationRunListeners.java:64)
at java.base/java.lang.Iterable.forEach(Iterable.java:75)
at org.springframework.boot.SpringApplicationRunListeners.doWithListeners(SpringApplicationRunListeners.java:118)
at org.springframework.boot.SpringApplicationRunListeners.doWithListeners(SpringApplicationRunListeners.java:112)
at org.springframework.boot.SpringApplicationRunListeners.environmentPrepared(SpringApplicationRunListeners.java:63)
at org.springframework.boot.SpringApplication.prepareEnvironment(SpringApplication.java:352)
at org.springframework.boot.SpringApplication.run(SpringApplication.java:303)
at org.springframework.boot.builder.SpringApplicationBuilder.run(SpringApplicationBuilder.java:150)
at com.faforever.client.FafClientApplication.init(FafClientApplication.java:80)
at com.sun.javafx.application.LauncherImpl.launchApplication1(LauncherImpl.java:825)
at com.sun.javafx.application.LauncherImpl.lambda$launchApplication$2(LauncherImpl.java:196)
at java.base/java.lang.Thread.run(Thread.java:833)
Caused by: java.util.regex.PatternSyntaxException: Unclosed group near index 73
C:/Users/STRIX(~1/AppData/Local/Temp//spring.log.\d{4}-\d{2}-\d{2}.\d+.gz
at java.base/java.util.regex.Pattern.error(Pattern.java:2028)
at java.base/java.util.regex.Pattern.accept(Pattern.java:1878)
at java.base/java.util.regex.Pattern.group0(Pattern.java:3053)
at java.base/java.util.regex.Pattern.sequence(Pattern.java:2124)
at java.base/java.util.regex.Pattern.expr(Pattern.java:2069)
at java.base/java.util.regex.Pattern.compile(Pattern.java:1783)
at java.base/java.util.regex.Pattern.<init>(Pattern.java:1430)
at java.base/java.util.regex.Pattern.compile(Pattern.java:1069)
at java.base/java.util.regex.Pattern.matches(Pattern.java:1174)
at java.base/java.lang.String.matches(String.java:2839)
at ch.qos.logback.core.rolling.RollingFileAppender.checkForFileAndPatternCollisions(RollingFileAppender.java:110)
at ch.qos.logback.core.rolling.RollingFileAppender.start(RollingFileAppender.java:81)
at ch.qos.logback.core.model.processor.AppenderModelHandler.postHandle(AppenderModelHandler.java:84)
at ch.qos.logback.core.model.processor.DefaultProcessor.secondPhaseTraverse(DefaultProcessor.java:257)
at ch.qos.logback.core.model.processor.DefaultProcessor.secondPhaseTraverse(DefaultProcessor.java:253)
at ch.qos.logback.core.model.processor.DefaultProcessor.traversalLoop(DefaultProcessor.java:90)
at ch.qos.logback.core.model.processor.DefaultProcessor.process(DefaultProcessor.java:106)
at ch.qos.logback.core.joran.GenericXMLConfigurator.processModel(GenericXMLConfigurator.java:200)
at org.springframework.boot.logging.logback.SpringBootJoranConfigurator.processModel(SpringBootJoranConfigurator.java:122)
at ch.qos.logback.core.joran.GenericXMLConfigurator.doConfigure(GenericXMLConfigurator.java:166)
at ch.qos.logback.core.joran.GenericXMLConfigurator.doConfigure(GenericXMLConfigurator.java:122)
at ch.qos.logback.core.joran.GenericXMLConfigurator.doConfigure(GenericXMLConfigurator.java:65)
at org.springframework.boot.logging.logback.LogbackLoggingSystem.configureByResourceUrl(LogbackLoggingSystem.java:265)
at org.springframework.boot.logging.logback.LogbackLoggingSystem.loadConfiguration(LogbackLoggingSystem.java:239)
... 25 more
Exception in Application init method
java.lang.RuntimeException: Exception in Application init method
at com.sun.javafx.application.LauncherImpl.launchApplication1(LauncherImpl.java:896)
at com.sun.javafx.application.LauncherImpl.lambda$launchApplication$2(LauncherImpl.java:196)
at java.base/java.lang.Thread.run(Thread.java:833)
Caused by: java.lang.IllegalStateException: java.lang.IllegalStateException: Could not initialize Logback logging from classpath:logback-spring.xml
at org.springframework.boot.context.logging.LoggingApplicationListener.initializeSystem(LoggingApplicationListener.java:347)
at org.springframework.boot.context.logging.LoggingApplicationListener.initialize(LoggingApplicationListener.java:298)
at org.springframework.boot.context.logging.LoggingApplicationListener.onApplicationEnvironmentPreparedEvent(LoggingApplicationListener.java:246)
at org.springframework.boot.context.logging.LoggingApplicationListener.onApplicationEvent(LoggingApplicationListener.java:223)
at org.springframework.context.event.SimpleApplicationEventMulticaster.doInvokeListener(SimpleApplicationEventMulticaster.java:176)
at org.springframework.context.event.SimpleApplicationEventMulticaster.invokeListener(SimpleApplicationEventMulticaster.java:169)
at org.springframework.context.event.SimpleApplicationEventMulticaster.multicastEvent(SimpleApplicationEventMulticaster.java:143)
at org.springframework.context.event.SimpleApplicationEventMulticaster.multicastEvent(SimpleApplicationEventMulticaster.java:131)
at org.springframework.boot.context.event.EventPublishingRunListener.multicastInitialEvent(EventPublishingRunListener.java:136)
at org.springframework.boot.context.event.EventPublishingRunListener.environmentPrepared(EventPublishingRunListener.java:81)
at org.springframework.boot.SpringApplicationRunListeners.lambda$environmentPrepared$2(SpringApplicationRunListeners.java:64)
at java.base/java.lang.Iterable.forEach(Iterable.java:75)
at org.springframework.boot.SpringApplicationRunListeners.doWithListeners(SpringApplicationRunListeners.java:118)
at org.springframework.boot.SpringApplicationRunListeners.doWithListeners(SpringApplicationRunListeners.java:112)
at org.springframework.boot.SpringApplicationRunListeners.environmentPrepared(SpringApplicationRunListeners.java:63)
at org.springframework.boot.SpringApplication.prepareEnvironment(SpringApplication.java:352)
at org.springframework.boot.SpringApplication.run(SpringApplication.java:303)
at org.springframework.boot.builder.SpringApplicationBuilder.run(SpringApplicationBuilder.java:150)
at com.faforever.client.FafClientApplication.init(FafClientApplication.java:80)
at com.sun.javafx.application.LauncherImpl.launchApplication1(LauncherImpl.java:825)
... 2 more
Caused by: java.lang.IllegalStateException: Could not initialize Logback logging from classpath:logback-spring.xml
at org.springframework.boot.logging.logback.LogbackLoggingSystem.loadConfiguration(LogbackLoggingSystem.java:242)
at org.springframework.boot.logging.AbstractLoggingSystem.initializeWithSpecificConfig(AbstractLoggingSystem.java:66)
at org.springframework.boot.logging.AbstractLoggingSystem.initialize(AbstractLoggingSystem.java:57)
at org.springframework.boot.logging.logback.LogbackLoggingSystem.initialize(LogbackLoggingSystem.java:188)
at org.springframework.boot.context.logging.LoggingApplicationListener.initializeSystem(LoggingApplicationListener.java:335)
... 21 more
Caused by: java.util.regex.PatternSyntaxException: Unclosed group near index 73
C:/Users/STRIX(~1/AppData/Local/Temp//spring.log.\d{4}-\d{2}-\d{2}.\d+.gz
at java.base/java.util.regex.Pattern.error(Pattern.java:2028)
at java.base/java.util.regex.Pattern.accept(Pattern.java:1878)
at java.base/java.util.regex.Pattern.group0(Pattern.java:3053)
at java.base/java.util.regex.Pattern.sequence(Pattern.java:2124)
at java.base/java.util.regex.Pattern.expr(Pattern.java:2069)
at java.base/java.util.regex.Pattern.compile(Pattern.java:1783)
at java.base/java.util.regex.Pattern.<init>(Pattern.java:1430)
at java.base/java.util.regex.Pattern.compile(Pattern.java:1069)
at java.base/java.util.regex.Pattern.matches(Pattern.java:1174)
at java.base/java.lang.String.matches(String.java:2839)
at ch.qos.logback.core.rolling.RollingFileAppender.checkForFileAndPatternCollisions(RollingFileAppender.java:110)
at ch.qos.logback.core.rolling.RollingFileAppender.start(RollingFileAppender.java:81)
at ch.qos.logback.core.model.processor.AppenderModelHandler.postHandle(AppenderModelHandler.java:84)
at ch.qos.logback.core.model.processor.DefaultProcessor.secondPhaseTraverse(DefaultProcessor.java:257)
at ch.qos.logback.core.model.processor.DefaultProcessor.secondPhaseTraverse(DefaultProcessor.java:253)
at ch.qos.logback.core.model.processor.DefaultProcessor.traversalLoop(DefaultProcessor.java:90)
at ch.qos.logback.core.model.processor.DefaultProcessor.process(DefaultProcessor.java:106)
at ch.qos.logback.core.joran.GenericXMLConfigurator.processModel(GenericXMLConfigurator.java:200)
at org.springframework.boot.logging.logback.SpringBootJoranConfigurator.processModel(SpringBootJoranConfigurator.java:122)
at ch.qos.logback.core.joran.GenericXMLConfigurator.doConfigure(GenericXMLConfigurator.java:166)
at ch.qos.logback.core.joran.GenericXMLConfigurator.doConfigure(GenericXMLConfigurator.java:122)
at ch.qos.logback.core.joran.GenericXMLConfigurator.doConfigure(GenericXMLConfigurator.java:65)
at org.springframework.boot.logging.logback.LogbackLoggingSystem.configureByResourceUrl(LogbackLoggingSystem.java:265)
at org.springframework.boot.logging.logback.LogbackLoggingSystem.loadConfiguration(LogbackLoggingSystem.java:239)
... 25 more

@uveso said in AI-Uveso (v98) - AI mod for FAForever:

Update 10.Oct.2021(v98)

• Fix: compatibility patch for insignificant units test. (needed, If you play FAFdevelop)

Got any plans for v100? Strippers and/or booze?

3724 SEEMS TO HAVE FIXED THE ISSUE.

@dddx said in BlackOpsFAF-Unleashed only for FAF v19:

@uveso nvm, if this (v18) were an issue it would have manifested long ago.

I can report the same projectile error with the Juggernaut battlestation unit BEL0307.

Anything that uses the "Railgun01" projectile is affected. I found like 5 units that use it (they're all UEF units).

I vaguely recall the old score being about 120. Now it's reading 108 to 102.

It's a 5600X with 3600 ram. I have the fclock at 1800 (max that that this Zen generation can stablely go). Nothing is traditionally OCed since you don't do that with Zen CPUs.

@mr_blastman said in Serious issues with new update, please revert.:

Nvidia fix can probably be removed now?

Yeah, it's been fixed for more than half a year. They plastered it all over the client's frontpage. Kinda hard to miss it.

@jip Considering I know little about the FAF integration level, so, this is appreciated. The sooner a hotfix goes out, the happier I'll be.

All that I know is that the Railgun01 projectile isn't native to Supcom, and it's borked on units that use it.

@jip As implied, the unit is originally from the BlackOps line of mods. Yes, it is the Citadel MK II.

The unitpack, I'm talking about where I noticed the issue from, is Mixed Combat Pack (MCP): https://github.com/SmalkiGroove/mcp-mod . MCP mixes together popular units, of various untipacks, and bugfixes/rebalances them together for one mod (TotalMayhem is notorious for having more powerful units vs. vanilla). My main interest in the mod is the backbone programming work he did, and notsomuch it being a convenient unitpack in one mod.

I did check over the BP file of his version of the Citadel, and it's fine. Here's a Winmerge report showing the differences: Citidel differences.7z . The left column is basically Uveso's BO release, and the right column is from MCP. The differences are just unit stats, and sourcing to make the unit work in his mod. And yes, I did follow-up on the Railgun01 files, and didn't see any differences there over Uveso's BO release.

I also mentioned running my standard mod array testing this (this doesn't include MCP - I only recently discovered it this past week). I ran a sandbox game, and this is where the screenshot came from. All those projectiles are "stuck".

I will see if any of my other mods are interfering with this, but I'm raising doubts. When I ran MCP, for my LAN session, the only other stuff running was basically QOL stuff. This seems to be something caused by the recent patches. I don't recall seeing this issue, beforehand, with the Citadel.

@uveso I'm not sure what you guys did in recent patches (3721+), but any unit using the Railgun01 projectile is borked. The particle effect won't go away, and it builds up in the sim, and lags the whole game. My last LAN game had the Citadel in it (via MCP, but I confirmed the problem on regular BlackOps game, too), and I had to constantly run the "Purge Projectiles" command in any attempt to try to finish the game.

Do you know of any short workaround outside of the obvious (banning units, etc)?