• Blitz Shadow Player
  • Caius
  • redboot
  • Rules
  • Chain of Command
  • Members
  • Supported Ladders & Games
  • Downloads


JTCS 2.04 BETA
09-02-2025, 04:34 PM, (This post was last modified: 09-03-2025, 03:35 PM by Crossroads.)
#11
RE: JTCS 2.04 BETA
Just to be specific on the question on this proposed tweak: the only additional intel edit: helper presented there is the text "Hard target".

Targeting is one of the most used features in this game so that is why I am asking if you all want this or not. IF you prefer how it is at the moment that is perfectly good and I will leave it untouched. Just thought to query your minds.
Visit us at CSLegion.com
Quote this message in a reply
09-02-2025, 09:54 PM,
#12
RE: JTCS 2.04 BETA
I'm with OJW. Too much info.
If you made it a option is one thing. Adding it as a part of the game is not for me.

Farmer

HSL
Quote this message in a reply
09-02-2025, 11:56 PM,
#13
RE: JTCS 2.04 BETA
Hello All, 

Make that a third for keep as is. 

Sometimes less is more. 

Erik
Quote this message in a reply
09-03-2025, 12:31 AM,
#14
RE: JTCS 2.04 BETA
Keep in mind, those details would be if Fog of War is NOT enabled.
Send this user an email
Quote this message in a reply
09-03-2025, 04:07 AM,
#15
RE: JTCS 2.04 BETA
All good, I am happy to leave it as it is. Just thought to ask as personally I am liking this a lot as I never remember in "20/7" text for instance which value is which.
Visit us at CSLegion.com
Quote this message in a reply
09-03-2025, 06:15 AM,
#16
RE: JTCS 2.04 BETA
(09-03-2025, 12:31 AM)Jason Petho Wrote: Keep in mind, those details would be if Fog of War is NOT enabled.

Yes, that is what I meant!  Big Grin

Farmer

HSL
Quote this message in a reply
09-03-2025, 03:46 PM, (This post was last modified: 09-03-2025, 08:12 PM by Crossroads.)
#17
RE: JTCS 2.04 BETA
All good then, I will compile the 2.05 Official Release exes to Matrix this weekend with no new additions.

The star of the new code always was the code Matrix provided to prevent white screen issues when launching the game main windows. And as Jason found out, renaming rs.exe to risun.exe (and modifying the Main Menu to invoke the newly named exe) to prevent Nvidia App overlay issues.

It took a lot of time to get here, but now we have the source code available for JTCS as well, although it is stuck in Visual Studio 2008 environment that is quite old now. Better not to rock the boat with it, and let us release the 2.05 with the fixes that are there.
Visit us at CSLegion.com
Quote this message in a reply
Yesterday, 06:26 AM,
#18
RE: JTCS 2.04 BETA
Hello All, 

Jason, I sent you an email that I am having with an RS scenario. 

Also, in the scenario Coup de Main.  The German commander 2 is not linked to any units. 

Please let me know what you find. 

Erik
Quote this message in a reply
Yesterday, 01:57 PM,
#19
RE: JTCS 2.04 BETA
Good day, Erik!

Thank you for the heads up, I appreciate it!

I added a commander to the organization. Looks like the original org file was added to at a later date and it was misplaced. It will be included in the final. PLEASE let me know if you find any other issues! Final deadline is the 9th

As for the Rising Sun scenario, I'll be taking a look tomorrow night. Thank you for sending it over.

Jason Petho
Send this user an email
Quote this message in a reply
Today, 12:02 AM, (This post was last modified: Today, 12:07 AM by Jason Petho.)
#20
RE: JTCS 2.04 BETA
I went and double checked the scenario files to see if this was a problem elsewhere and found that 7 scenarios have this problem in various degrees of terribleness. 

If you open the scenario file in a text editor and see a negative one, like in the example below, that means that the unit in question is not in the org file and is missing the org ID.  The most common cause for this is that an older org file with the same name replaced the newer file.

0 13 129 1062 -1 2 4 3 100 6 0 16384 3 3 3

The solution to this is to find a suitable unit in the org file and replace the -1 with the proper unique ID, which you can pick one, just make sure it isn't duplicated elsewhere in the file. 

If the unit is not in the org file, it can be added in a text editor and given a new unique ID. 

(from the org file)
                        P1062 5781 8 Trucks

So then the fixed line would like this:

0 13 129 1062 5781 2 4 3 100 6 0 16384 3 3 3

It's tedious as hell, but it is possible to remedy. I'll be doing this the next few days. 
Send this user an email
Quote this message in a reply


Forum Jump:


Users browsing this thread: 1 Guest(s)