Author Topic: BETA RELEASE: Revenge Final Conflict  (Read 11485 times)

0 Members and 1 Guest are viewing this topic.

Offline Bryan See

  • Has anyone really been far as decided to use even go want to do look more like?
  • 210
  • Trying to redeem.
    • Skype
    • Steam
    • Twitter
Re: RELEASE: fixed 100% revenge
Two technical problems:

1-I don't see the Blackstar primary weapon available on the weapon select screen.  However, when I put the Prometheus Retrofit cannon on a fighter, when I start the mission then I get the Blackstar.

2-I have also ran into a technical problem on the mission "Out Of The Blue".  I used the TAG-D on ships but nothing happens.  I hear the sound of a heavy beam cannon but I don't see the beam.  Ships don't get damaged.



I had to die 5X to get through that mission where enemy ships wouldn't get damaged.

I started chapter 2 and ran into another problem:
After beating the mission "Beginning Of All", it wouldn't let me go onto the next mission at all.  I got this error message:

Error: 041-Revenge.fs2(line 85):
Error: Required token = [#Objects] or [$], found [;! 1 total].

File: parselo.cpp
Line: 290

ntdll.dll! NtWaitForSingleObject + 10 bytes
KERNELBASE.dll! WaitForSingleObjectEx + 156 bytes
fs2_open_3_8_1_20171031_e2d8502_x64_SSE2.exe! <no symbol>
fs2_open_3_8_1_20171031_e2d8502_x64_SSE2.exe! <no symbol>
fs2_open_3_8_1_20171031_e2d8502_x64_SSE2.exe! <no symbol>
fs2_open_3_8_1_20171031_e2d8502_x64_SSE2.exe! <no symbol>
fs2_open_3_8_1_20171031_e2d8502_x64_SSE2.exe! <no symbol>
fs2_open_3_8_1_20171031_e2d8502_x64_SSE2.exe! <no symbol>
fs2_open_3_8_1_20171031_e2d8502_x64_SSE2.exe! <no symbol>
fs2_open_3_8_1_20171031_e2d8502_x64_SSE2.exe! <no symbol>
fs2_open_3_8_1_20171031_e2d8502_x64_SSE2.exe! <no symbol>
fs2_open_3_8_1_20171031_e2d8502_x64_SSE2.exe! <no symbol>
fs2_open_3_8_1_20171031_e2d8502_x64_SSE2.exe! <no symbol>
fs2_open_3_8_1_20171031_e2d8502_x64_SSE2.exe! <no symbol>
fs2_open_3_8_1_20171031_e2d8502_x64_SSE2.exe! <no symbol>
fs2_open_3_8_1_20171031_e2d8502_x64_SSE2.exe! <no symbol>
fs2_open_3_8_1_20171031_e2d8502_x64_SSE2.exe! <no symbol>
fs2_open_3_8_1_20171031_e2d8502_x64_SSE2.exe! <no symbol>
fs2_open_3_8_1_20171031_e2d8502_x64_SSE2.exe! <no symbol>
fs2_open_3_8_1_20171031_e2d8502_x64_SSE2.exe! <no symbol>
fs2_open_3_8_1_20171031_e2d8502_x64_SSE2.exe! <no symbol>
fs2_open_3_8_1_20171031_e2d8502_x64_SSE2.exe! <no symbol>
kernel32.dll! BaseThreadInitThunk + 13 bytes
ntdll.dll! RtlUserThreadStart + 29 bytes


I'll check on it.
Bryan See - My FreeSpace Wiki User Page (Talk, Contributions)

Campaigns:
FreeSpace: Reunited - Shattered Stars

Ships:
GTS Hygeia, GTT Argo, SC Raguel

 

Offline CT27

  • 210
Re: RELEASE: fixed 100% revenge
Here's a log if it helps.

[attachment stolen by Russian hackers]

 

Offline AdmiralRalwood

  • 211
  • The Cthulhu programmer himself!
    • Skype
    • Steam
    • Twitter
Re: RELEASE: fixed 100% revenge
That error means there's an unclosed quotation mark earlier in the mission file than the line it's erroring on.
Ph'nglui mglw'nafh Codethulhu GitHub wgah'nagl fhtagn.

schrödinbug (noun) - a bug that manifests itself in running software after a programmer notices that the code should never have worked in the first place.

When you gaze long into BMPMAN, BMPMAN also gazes into you.

"I am one of the best FREDders on Earth" -General Battuta

<Aesaar> literary criticism is vladimir putin

<MageKing17> "There's probably a reason the code is the way it is" is a very dangerous line of thought. :P
<MageKing17> Because the "reason" often turns out to be "nobody noticed it was wrong".
(the very next day)
<MageKing17> this ****ing code did it to me again
<MageKing17> "That doesn't really make sense to me, but I'll assume it was being done for a reason."
<MageKing17> **** ME
<MageKing17> THE REASON IS PEOPLE ARE STUPID
<MageKing17> ESPECIALLY ME

<MageKing17> God damn, I do not understand how this is breaking.
<MageKing17> Everything points to "this should work fine", and yet it's clearly not working.
<MjnMixael> 2 hours later... "God damn, how did this ever work at all?!"
(...)
<MageKing17> so
<MageKing17> more than two hours
<MageKing17> but once again we have reached the inevitable conclusion
<MageKing17> How did this code ever work in the first place!?

<@The_E> Welcome to OpenGL, where standards compliance is optional, and error reporting inconsistent

<MageKing17> It was all working perfectly until I actually tried it on an actual mission.

<IronWorks> I am useful for FSO stuff again. This is a red-letter day!
* z64555 erases "Thursday" and rewrites it in red ink

<MageKing17> TIL the entire homing code is held up by shoestrings and duct tape, basically.

 

Offline CT27

  • 210
Re: RELEASE: fixed 100% revenge
I got  that error for a number of different lines.

 

Offline AdmiralRalwood

  • 211
  • The Cthulhu programmer himself!
    • Skype
    • Steam
    • Twitter
Re: RELEASE: fixed 100% revenge
...Okay, so there are a lot of unclosed quotation marks. The problem is still the same.
Ph'nglui mglw'nafh Codethulhu GitHub wgah'nagl fhtagn.

schrödinbug (noun) - a bug that manifests itself in running software after a programmer notices that the code should never have worked in the first place.

When you gaze long into BMPMAN, BMPMAN also gazes into you.

"I am one of the best FREDders on Earth" -General Battuta

<Aesaar> literary criticism is vladimir putin

<MageKing17> "There's probably a reason the code is the way it is" is a very dangerous line of thought. :P
<MageKing17> Because the "reason" often turns out to be "nobody noticed it was wrong".
(the very next day)
<MageKing17> this ****ing code did it to me again
<MageKing17> "That doesn't really make sense to me, but I'll assume it was being done for a reason."
<MageKing17> **** ME
<MageKing17> THE REASON IS PEOPLE ARE STUPID
<MageKing17> ESPECIALLY ME

<MageKing17> God damn, I do not understand how this is breaking.
<MageKing17> Everything points to "this should work fine", and yet it's clearly not working.
<MjnMixael> 2 hours later... "God damn, how did this ever work at all?!"
(...)
<MageKing17> so
<MageKing17> more than two hours
<MageKing17> but once again we have reached the inevitable conclusion
<MageKing17> How did this code ever work in the first place!?

<@The_E> Welcome to OpenGL, where standards compliance is optional, and error reporting inconsistent

<MageKing17> It was all working perfectly until I actually tried it on an actual mission.

<IronWorks> I am useful for FSO stuff again. This is a red-letter day!
* z64555 erases "Thursday" and rewrites it in red ink

<MageKing17> TIL the entire homing code is held up by shoestrings and duct tape, basically.

 

Offline CT27

  • 210
Re: RELEASE: fixed 100% revenge
In any case, it's not letting me progress in the campaign.

 
Re: RELEASE: fixed 100% revenge
Bryan see gived me fake fixes ive tryied to play mission 14 but its broken i adk him to fix for me but he did send asame version 5 times in a row

 

Offline CT27

  • 210
Re: RELEASE: fixed 100% revenge
I also got this error when trying to play after "Beginning Of All" (mission 40)





Error: Cannot load mission -- for wing Alpha, ship ! 4 total
    is not present in #Objects section.

File: missionparse.cpp
Line: 4620

ntdll.dll! NtWaitForSingleObject + 10 bytes
KERNELBASE.dll! WaitForSingleObjectEx + 156 bytes
fs2_open_3_8_1_20171031_e2d8502_x64_SSE2.exe! <no symbol>
fs2_open_3_8_1_20171031_e2d8502_x64_SSE2.exe! <no symbol>
fs2_open_3_8_1_20171031_e2d8502_x64_SSE2.exe! <no symbol>
fs2_open_3_8_1_20171031_e2d8502_x64_SSE2.exe! <no symbol>
fs2_open_3_8_1_20171031_e2d8502_x64_SSE2.exe! <no symbol>
fs2_open_3_8_1_20171031_e2d8502_x64_SSE2.exe! <no symbol>
fs2_open_3_8_1_20171031_e2d8502_x64_SSE2.exe! <no symbol>
fs2_open_3_8_1_20171031_e2d8502_x64_SSE2.exe! <no symbol>
fs2_open_3_8_1_20171031_e2d8502_x64_SSE2.exe! <no symbol>
fs2_open_3_8_1_20171031_e2d8502_x64_SSE2.exe! <no symbol>
fs2_open_3_8_1_20171031_e2d8502_x64_SSE2.exe! <no symbol>
fs2_open_3_8_1_20171031_e2d8502_x64_SSE2.exe! <no symbol>
fs2_open_3_8_1_20171031_e2d8502_x64_SSE2.exe! <no symbol>
fs2_open_3_8_1_20171031_e2d8502_x64_SSE2.exe! <no symbol>
fs2_open_3_8_1_20171031_e2d8502_x64_SSE2.exe! <no symbol>
fs2_open_3_8_1_20171031_e2d8502_x64_SSE2.exe! <no symbol>
fs2_open_3_8_1_20171031_e2d8502_x64_SSE2.exe! <no symbol>
fs2_open_3_8_1_20171031_e2d8502_x64_SSE2.exe! <no symbol>
kernel32.dll! BaseThreadInitThunk + 13 bytes
ntdll.dll! RtlUserThreadStart + 29 bytes

 

Offline Novachen

  • 29
  • The one and only capella supernova
    • Twitter
Re: RELEASE: fixed 100% revenge
Well, actually it seems, that this upgrade was not playtested before it's release...
Female FreeSpace 2 pilot since 1999.
Global moderator in the German FreeSpace Galaxy Forum.

Responsible for the german translation project FreiRaum - FreeSpace auf Deutsch.
Also responsible for the Nova Upgrade Project, which upgrades and fix older campaigns to make them play- and solveable again with current builds and MediaVPs.

Release List:
German Translations:
Awakenings, Between the Ashes 1 (former), Deneb III, FreeSpace 2 (in development), FreeSpace Port, Silent Threat: Reborn & The Destiny of Peace

Nova Upgrades:
A Walk in the Sun, Into the Halls of Valhalla, Luyten Civil War, Renegade Resurgence, Revenge: Final Conflict (in development), Rogues!, Shadow Genesis (de-facto), Storm Front Saga (former), The Deuterium Connection, Venice Mirror & What If: Another Great War (former)

 

Offline CT27

  • 210
Re: RELEASE: fixed 100% revenge
I also couldn't play mission 41 through the techroom either.  I got the same sets of errors.

 
Re: RELEASE: fixed 100% revenge
Given the amount of bugs appearing over this campaign, wouldn't it be reasonable to recall it "Open Beta" or something like that until all new errors are fixed?

 
Re: RELEASE: fixed 100% revenge
yeach but you know

 
 

Offline CT27

  • 210
Re: RELEASE: fixed 100% revenge
Since I couldn't advance beyond a certain point in chapter 2 I played the chapter 2 missions through the tech room.

I then played chapter 3.  That had relatively few technical errors from what I remember.  However, a set of missions near the end was really repetitive. 
Spoiler:
Disable a Lucifer, destroy a Lucifier, rinse and repeat a few times got kind of boring.  IMO there should have only been about three Lucifers so that you didn't need to play a carbon copy of the missions multiple times.


A question about the final combat mission though:  Is it possible to
Spoiler:
save the Malevolence if you destroy Sathanas beams quickly enough
?

 

Offline Novachen

  • 29
  • The one and only capella supernova
    • Twitter
Re: RELEASE: fixed 100% revenge
Well...

i think we should collect all errors we have so far :).

In the attachment are fixes for 40 and 41 because both missions were reported.
Create a data/missions folder in your revenge folder and paste them in.


By the way... what the hell is wrong with this english translation? Why are all weapon descriptions still in german?  :lol:
Even i also hoped someone has fixed the mess in the weapons.tbl from the original, because all the table edits were created with an Hex Editor back then, because the original creator did know nothing about VP extraction tools.


And as i talk about the original... i am still curious if the original german version of this is still available to create a proper multi-language version?

[attachment stolen by Russian hackers]
« Last Edit: March 08, 2018, 07:34:31 pm by Novachen »
Female FreeSpace 2 pilot since 1999.
Global moderator in the German FreeSpace Galaxy Forum.

Responsible for the german translation project FreiRaum - FreeSpace auf Deutsch.
Also responsible for the Nova Upgrade Project, which upgrades and fix older campaigns to make them play- and solveable again with current builds and MediaVPs.

Release List:
German Translations:
Awakenings, Between the Ashes 1 (former), Deneb III, FreeSpace 2 (in development), FreeSpace Port, Silent Threat: Reborn & The Destiny of Peace

Nova Upgrades:
A Walk in the Sun, Into the Halls of Valhalla, Luyten Civil War, Renegade Resurgence, Revenge: Final Conflict (in development), Rogues!, Shadow Genesis (de-facto), Storm Front Saga (former), The Deuterium Connection, Venice Mirror & What If: Another Great War (former)

 
Re: RELEASE: fixed 100% revenge
i have troube with mission 17
Assert: "(size_t)handle < GL_buffer_objects.size()"
File: gropengltnl.cpp
Line: 299

ntdll.dll! NtWaitForSingleObject + 20 bytes
KERNELBASE.dll! WaitForSingleObjectEx + 159 bytes
fs2_open_3_8_1_20180213_a0a8812_x64_SSE2-FASTDBG.exe! SDL_main + 2769515 bytes
fs2_open_3_8_1_20180213_a0a8812_x64_SSE2-FASTDBG.exe! SDL_main + 3885052 bytes
fs2_open_3_8_1_20180213_a0a8812_x64_SSE2-FASTDBG.exe! SDL_main + 3328601 bytes
fs2_open_3_8_1_20180213_a0a8812_x64_SSE2-FASTDBG.exe! SDL_main + 3935606 bytes
fs2_open_3_8_1_20180213_a0a8812_x64_SSE2-FASTDBG.exe! <no symbol>
fs2_open_3_8_1_20180213_a0a8812_x64_SSE2-FASTDBG.exe! <no symbol>
fs2_open_3_8_1_20180213_a0a8812_x64_SSE2-FASTDBG.exe! <no symbol>
fs2_open_3_8_1_20180213_a0a8812_x64_SSE2-FASTDBG.exe! <no symbol>
fs2_open_3_8_1_20180213_a0a8812_x64_SSE2-FASTDBG.exe! <no symbol>
fs2_open_3_8_1_20180213_a0a8812_x64_SSE2-FASTDBG.exe! <no symbol>
fs2_open_3_8_1_20180213_a0a8812_x64_SSE2-FASTDBG.exe! <no symbol>
fs2_open_3_8_1_20180213_a0a8812_x64_SSE2-FASTDBG.exe! <no symbol>
fs2_open_3_8_1_20180213_a0a8812_x64_SSE2-FASTDBG.exe! <no symbol>
fs2_open_3_8_1_20180213_a0a8812_x64_SSE2-FASTDBG.exe! <no symbol>
fs2_open_3_8_1_20180213_a0a8812_x64_SSE2-FASTDBG.exe! SDL_main + 3325973 bytes
fs2_open_3_8_1_20180213_a0a8812_x64_SSE2-FASTDBG.exe! SDL_main + 3328893 bytes
fs2_open_3_8_1_20180213_a0a8812_x64_SSE2-FASTDBG.exe! SDL_main + 3935606 bytes
fs2_open_3_8_1_20180213_a0a8812_x64_SSE2-FASTDBG.exe! SDL_main + 4069696 bytes
fs2_open_3_8_1_20180213_a0a8812_x64_SSE2-FASTDBG.exe! <no symbol>
fs2_open_3_8_1_20180213_a0a8812_x64_SSE2-FASTDBG.exe! <no symbol>
fs2_open_3_8_1_20180213_a0a8812_x64_SSE2-FASTDBG.exe! <no symbol>
fs2_open_3_8_1_20180213_a0a8812_x64_SSE2-FASTDBG.exe! <no symbol>
fs2_open_3_8_1_20180213_a0a8812_x64_SSE2-FASTDBG.exe! <no symbol>
fs2_open_3_8_1_20180213_a0a8812_x64_SSE2-FASTDBG.exe! <no symbol>
[...]
[ This info is in the clipboard so you can paste it somewhere now ]


Use Debug to break into Debugger, Exit will close the application.

ntdll.dll! NtWaitForSingleObject + 20 bytes
KERNELBASE.dll! WaitForSingleObjectEx + 159 bytes
fs2_open_3_8_1_20180213_a0a8812_x64_SSE2-FASTDBG.exe! SDL_main + 2769515 bytes
fs2_open_3_8_1_20180213_a0a8812_x64_SSE2-FASTDBG.exe! SDL_main + 3885052 bytes
fs2_open_3_8_1_20180213_a0a8812_x64_SSE2-FASTDBG.exe! SDL_main + 3325350 bytes
fs2_open_3_8_1_20180213_a0a8812_x64_SSE2-FASTDBG.exe! SDL_main + 3328893 bytes
fs2_open_3_8_1_20180213_a0a8812_x64_SSE2-FASTDBG.exe! SDL_main + 3935606 bytes
fs2_open_3_8_1_20180213_a0a8812_x64_SSE2-FASTDBG.exe! <no symbol>
fs2_open_3_8_1_20180213_a0a8812_x64_SSE2-FASTDBG.exe! <no symbol>
fs2_open_3_8_1_20180213_a0a8812_x64_SSE2-FASTDBG.exe! <no symbol>
fs2_open_3_8_1_20180213_a0a8812_x64_SSE2-FASTDBG.exe! <no symbol>
fs2_open_3_8_1_20180213_a0a8812_x64_SSE2-FASTDBG.exe! <no symbol>
fs2_open_3_8_1_20180213_a0a8812_x64_SSE2-FASTDBG.exe! <no symbol>
fs2_open_3_8_1_20180213_a0a8812_x64_SSE2-FASTDBG.exe! <no symbol>
fs2_open_3_8_1_20180213_a0a8812_x64_SSE2-FASTDBG.exe! <no symbol>
fs2_open_3_8_1_20180213_a0a8812_x64_SSE2-FASTDBG.exe! <no symbol>
fs2_open_3_8_1_20180213_a0a8812_x64_SSE2-FASTDBG.exe! <no symbol>
fs2_open_3_8_1_20180213_a0a8812_x64_SSE2-FASTDBG.exe! SDL_main + 3325973 bytes
fs2_open_3_8_1_20180213_a0a8812_x64_SSE2-FASTDBG.exe! SDL_main + 3328893 bytes
fs2_open_3_8_1_20180213_a0a8812_x64_SSE2-FASTDBG.exe! SDL_main + 3935606 bytes
fs2_open_3_8_1_20180213_a0a8812_x64_SSE2-FASTDBG.exe! SDL_main + 4069696 bytes
fs2_open_3_8_1_20180213_a0a8812_x64_SSE2-FASTDBG.exe! <no symbol>
fs2_open_3_8_1_20180213_a0a8812_x64_SSE2-FASTDBG.exe! <no symbol>
fs2_open_3_8_1_20180213_a0a8812_x64_SSE2-FASTDBG.exe! <no symbol>
fs2_open_3_8_1_20180213_a0a8812_x64_SSE2-FASTDBG.exe! <no symbol>
fs2_open_3_8_1_20180213_a0a8812_x64_SSE2-FASTDBG.exe! <no symbol>
fs2_open_3_8_1_20180213_a0a8812_x64_SSE2-FASTDBG.exe! <no symbol>
fs2_open_3_8_1_20180213_a0a8812_x64_SSE2-FASTDBG.exe! <no symbol>
fs2_open_3_8_1_20180213_a0a8812_x64_SSE2-FASTDBG.exe! <no symbol>
fs2_open_3_8_1_20180213_a0a8812_x64_SSE2-FASTDBG.exe! SDL_main + 3325973 bytes
fs2_open_3_8_1_20180213_a0a8812_x64_SSE2-FASTDBG.exe! SDL_main + 3329757 bytes
fs2_open_3_8_1_20180213_a0a8812_x64_SSE2-FASTDBG.exe! SDL_main + 1812475 bytes
fs2_open_3_8_1_20180213_a0a8812_x64_SSE2-FASTDBG.exe! SDL_main + 1815693 bytes
fs2_open_3_8_1_20180213_a0a8812_x64_SSE2-FASTDBG.exe! SDL_main + 1809660 bytes
fs2_open_3_8_1_20180213_a0a8812_x64_SSE2-FASTDBG.exe! SDL_main + 2698924 bytes
fs2_open_3_8_1_20180213_a0a8812_x64_SSE2-FASTDBG.exe! SDL_main + 66112 bytes
fs2_open_3_8_1_20180213_a0a8812_x64_SSE2-FASTDBG.exe! SDL_main + 18730 bytes
fs2_open_3_8_1_20180213_a0a8812_x64_SSE2-FASTDBG.exe! SDL_main + 1246665 bytes
fs2_open_3_8_1_20180213_a0a8812_x64_SSE2-FASTDBG.exe! SDL_main + 23234 bytes
fs2_open_3_8_1_20180213_a0a8812_x64_SSE2-FASTDBG.exe! SDL_main + 1247437 bytes
fs2_open_3_8_1_20180213_a0a8812_x64_SSE2-FASTDBG.exe! SDL_main + 14552 bytes
fs2_open_3_8_1_20180213_a0a8812_x64_SSE2-FASTDBG.exe! SDL_main + 130 bytes
fs2_open_3_8_1_20180213_a0a8812_x64_SSE2-FASTDBG.exe! <no symbol>
fs2_open_3_8_1_20180213_a0a8812_x64_SSE2-FASTDBG.exe! <no symbol>
fs2_open_3_8_1_20180213_a0a8812_x64_SSE2-FASTDBG.exe! <no symbol>
fs2_open_3_8_1_20180213_a0a8812_x64_SSE2-FASTDBG.exe! <no symbol>
fs2_open_3_8_1_20180213_a0a8812_x64_SSE2-FASTDBG.exe! <no symbol>
KERNEL32.DLL! BaseThreadInitThunk + 20 bytes
ntdll.dll! RtlUserThreadStart + 33 bytes


[attachment stolen by Russian hackers]

 

Offline Novachen

  • 29
  • The one and only capella supernova
    • Twitter
Re: RELEASE: fixed 100% revenge
So, the fix for mission 17.

If this is the quality Bryan See want to stand for... i do not look very positive to his projects  :(

[attachment stolen by Russian hackers]
Female FreeSpace 2 pilot since 1999.
Global moderator in the German FreeSpace Galaxy Forum.

Responsible for the german translation project FreiRaum - FreeSpace auf Deutsch.
Also responsible for the Nova Upgrade Project, which upgrades and fix older campaigns to make them play- and solveable again with current builds and MediaVPs.

Release List:
German Translations:
Awakenings, Between the Ashes 1 (former), Deneb III, FreeSpace 2 (in development), FreeSpace Port, Silent Threat: Reborn & The Destiny of Peace

Nova Upgrades:
A Walk in the Sun, Into the Halls of Valhalla, Luyten Civil War, Renegade Resurgence, Revenge: Final Conflict (in development), Rogues!, Shadow Genesis (de-facto), Storm Front Saga (former), The Deuterium Connection, Venice Mirror & What If: Another Great War (former)

 
Re: RELEASE: fixed 100% revenge
Well Bryan See made a good-looking HTL Amritaya and some Shivan frigate, he just didn't finished them :blah:

 

Offline Novachen

  • 29
  • The one and only capella supernova
    • Twitter
Re: RELEASE: fixed 100% revenge
As you reported a not working mission 14, too woutersmits, i looked into the three mission 14 this campaign have.

One of them used the retail weapon table as a template instead of the revenge one. I fixed this.

Actually i get the feeling, that i have to get the original version even more, to check all the missions if the player get the weapons he should have at this point in the campaign  :D


Also i predict, that i have to play all 88 missions by myself to find all errors this release have  :shaking:

[attachment stolen by Russian hackers]
« Last Edit: March 09, 2018, 07:54:12 am by Novachen »
Female FreeSpace 2 pilot since 1999.
Global moderator in the German FreeSpace Galaxy Forum.

Responsible for the german translation project FreiRaum - FreeSpace auf Deutsch.
Also responsible for the Nova Upgrade Project, which upgrades and fix older campaigns to make them play- and solveable again with current builds and MediaVPs.

Release List:
German Translations:
Awakenings, Between the Ashes 1 (former), Deneb III, FreeSpace 2 (in development), FreeSpace Port, Silent Threat: Reborn & The Destiny of Peace

Nova Upgrades:
A Walk in the Sun, Into the Halls of Valhalla, Luyten Civil War, Renegade Resurgence, Revenge: Final Conflict (in development), Rogues!, Shadow Genesis (de-facto), Storm Front Saga (former), The Deuterium Connection, Venice Mirror & What If: Another Great War (former)

 
Re: RELEASE: fixed 100% revenge
if you have time go ahead