Hard Light Productions Forums
Hosted Projects - Standalone => Diaspora => Topic started by: karajorma on January 14, 2014, 01:44:44 am
-
Okay everyone, here's the release candidate for Diaspora R1.1
R1.1 is meant to be the version of Diaspora we wanted to release originally but couldn't. Stuff we'd planned had to be cut out because we simply didn't have the staff or the time to implement or test it. The biggest change you'll notice is that we finally added the briefing animations we'd always wanted. Thanks a lot to David cgc for those (We should thank Matthew Haley for the DRADIS screens used as the basis of our animations). We've also ironed out a bunch of the bugs that were still present in 1.0.4. Hopefully no new ones have sprung up in their place.
If there are no new bugs reported, we'll bump this one up to the official patch release very soon. We're also planning a new installer for those who haven't got the game which will install the game and patch 1.1 at the same time.
As with previous patches, this patch does not require you to have earlier versions of the patch in order to work (and will in fact delete earlier versions).
Downloads
Windows (http://diaspora.fs2downloads.com/Diaspora_R1_Patch_1.1.exe)
Mac (Coming Soon)
Linux (Coming Soon)
Changelog
1.1
Add new briefing animations.
Add preliminary Spanish language support.
Fix a Mission 6 crash.
Updated Builds to r10280.
1.0.4
Fix an multiplayer issue with weapon convergence.
Fix an issue where the prometheus wouldn't depart
Add new animations for the volunteer for M3 screen
Fixed M6 breaking if Ion 1 is destroyed.
Added directive counts training missions.
1.0.3
Fix a crash in Mission 6.
Fix an AI bug with drone landings in Training Mission 2.
Fix a problem with Directives not appearing in Training Mission 2.
Add Directive counters to Training Mission 2.
Fix rotation issue with Raptor door.
Alter the timing for civilian jumps in Mission 5.
Adding more missing built in messages.
Fix lack of loading screen errors in debug.
Fix missing art for the MEC-A6 (training) in the techroom.
Fix #weak weapons appearing in the techroom in multiplayer.
Remove/disable debug events in Mission 5.
Add missing cache files.
Update credits file.
Fix issue where Cylon HUD crashes the standalone server.
Fix Mission 6 issues where the Prometheus could be destroyed.
1.0.2
Fix M6 crashes due to #weak weapons.
Fix M6 crashes due show ship using incorrect model when doing the sun ray test.
Added missing gauge for system messages to the HUD.
Fix issues with Multiplayer option screen (hard to see where to click).
Fix mission bugs with Indart survival.
Assign hotkeys to all mission critical fighters.
Minor changes to HUD gadgets.
Added fix to reset collision cache hashes when starting a new mission.
Added fix to properly clean out unnecessary objects in the new collision code.
(Windows) Fix an issue with the kills gauge vanishing.
Update missions for a bug\support for the new key bindings.
Added FS2NetD interface art and fixed all messages to not mention PXO.
-
Just poping in to say that the new briefing anims are A-awesome.
-
The plan to have them is many years old, but it was only once David cgc joined the team that we actually had someone with the time to make them.
That said, his animations turned out much better than my original impression of what they'd look like.
-
Hiiiiiiiiiiiiiiiiiiighlight
-
Finally got around to playing the new version, and I'd like to add my own praise for those sweet briefing animations.
-
Hiiiiiiiiiiiiiiiiiiighlight
It's only the release candidate, I'll highlight it as soon as it goes gold. We've already had one bug report so I'd like to have that issue fixed first.
-
Thanks, everybody. I'm glad the briefings well-received. Those were a lot of fun to do.
-
We've already had one bug report so I'd like to have that issue fixed first.
Just finished replaying the campaign with 1.1 and didn't encounter any bugs, myself! Seriously, David cgc, those briefing animations really complete the experience. Fantastic job.
-
Hey karajorma,
There seems to be a windows build, while there are no Linux or Mac downloads available ("coming soon")... Perhaps you could at least post a link to source code for us to build ourselves
Thanks
-
That is no longer necessary. You can use one of the mainline FSOpen releases to play Diaspora these days.
-
That is no longer necessary. You can use one of the mainline FSOpen releases to play Diaspora these days.
I mean the new Diaspora release not fs2_open
-
You can just grab a recent FreeSpace Open nightly build for Linux or Mac in the Nightly Builds subforum and it'll run Diaspora fine. Diaspora runs on FreeSpace Open.
-
Problem is that there's no download of 1.1 that doesn't come as a Windows executable yet.
-
Ohhhhh **** gotcha.
e: posting the source code won't help then
-
So is Diaspora's development only done with specific members?
-
People with gold Diaspora badges are members of the Diaspora team.
-
And sorry, I misunderstood your question. I thought it referred to the engine executable, not the patch installer.
-
Downloading; can't wait to try it after the kiddos go to bed!
-
Apparently the internet is currently down for most of the province I live in. So I can't post the required files but if someone wants to 7zip the files up you only really need the new files in Data/Movies and the 1.1 VP file.
-
People with gold Diaspora badges are members of the Diaspora team.
True, but anyone can help us develop the code. People can apply to join the team for other reasons by looking at the recruitment post.
And anyone can mod Diaspora themselves. Everything is under Creative Commons afterall
-
My antivirus refuses to go to the download page
Malware detected!
Access to this page has been blocked.
Anyone else having this problem?
-
Antivirus software heuristics really like to decide that FSO is malware. :doubt:
-
Apparently the internet is currently down for most of the province I live in. So I can't post the required files but if someone wants to 7zip the files up you only really need the new files in Data/Movies and the 1.1 VP file.
Are you addressing the Diaspora team? If not where can we get the new files and the 1.1 VP?
-
He's addressing anyone on Windows, who could use the .exe installer and then create .7zip archives accessible to anyone on Linux or Mac.
-
Since nobody else has done it yet:
http://deviance.duckish.net/downloads/Diaspora_1.1.7z
-
Since nobody else has done it yet:
http://deviance.duckish.net/downloads/Diaspora_1.1.7z
/me cheers!
-
Thanks a lot Ralwood.
-
Since nobody else has done it yet:
http://deviance.duckish.net/downloads/Diaspora_1.1.7z
Thanks a lot! BTW, do I copy the R1.1 patch VP file replacing the old 1.0.4 VP, or do I add them side by side?
-
My antivirus refuses to go to the download page
Malware detected!
Access to this page has been blocked.
Anyone else having this problem?
I had that problem when running Bitdefender while downloading the original Diaspora release. I had to disable bitdefender to unblock the download page. (Avast just gives me a warning that the file is rarely downloaded and may be dangerous, but it does not stop me.)
-
Since nobody else has done it yet:
http://deviance.duckish.net/downloads/Diaspora_1.1.7z
Thanks a lot! BTW, do I copy the R1.1 patch VP file replacing the old 1.0.4 VP, or do I add them side by side?
Delete 1.0.4. Everything in that VP is in the 1.1 VP.
-
Thanks for still updating and working on diaspora! that's great.
I like the new briefing animations, though I haven't seen them all yet, because I am working on my own 'Asheron campaign' missions the most.
After this update a couple of things changed in them as well... The fade in (when the mission starts) is always white now, and some of my landing events have stopped working :confused: :nervous:. Has something been changed in FRED that could be the cause of these 'bugs'?
Also the messages are closer to each other (different fond?), so they are quite difficult to read. It's quite irritating, since I don't have any voices in my missions.
I am working on the 10th mission now, the 11th will be the final Asheron campaign mission.
-
Thanks for still working on this. Shattered Memories was already a highly, highly polished campaign so these animations are a nice final touch.
-
Keep up the good work, everyone. I'd hope I will see Command Briefing cutscenes/animations.
-
Hate to bring this up but I am afraid you broke something with 1.1
In the first real mission (I skipped training, I know the game after all) I was unable to land in any of the bays. So as long as the landing procedure has not changed with this release (correct orientation, low speed, set her down) it is broken.
-
Can we get a confirmation on this? Also, what difficulty mode were you on? Since landings are different on medium and higher.
Same on the Ion destroyed bug because checking the mission in FRED it should be fine.
-
Hate to bring this up but I am afraid you broke something with 1.1
In the first real mission (I skipped training, I know the game after all) I was unable to land in any of the bays. So as long as the landing procedure has not changed with this release (correct orientation, low speed, set her down) it is broken.
That mission hasn't actually changed in 1.1 though. In fact it's barely changed in 1.0.3 which was the last time the mission was altered.
Did the mission definitely work before? If so, in which revision? Also, what do you mean when you say you couldn't land?
-
I've replayed the mission a couple of times from the techroom in 1.1, and I haven't had trouble landing.
EDIT - game difficulty was set to insane iirc
-
Last played this mission on 1.0.4 and it worked. Okay, I go back and play the tutorial on landing for higher difficulties to confirm this.
-
Can we get a confirmation on this? Also, what difficulty mode were you on? Since landings are different on medium and higher.
Same on the Ion destroyed bug because checking the mission in FRED it should be fine.
I've experienced this on the next mission (The Strike) on advanced difficulty when I tried to dock soon after the departure warning. I can't remember which landing pod I tried to land in but after touching down several times I couldn't dock. I'll have another look at it later today.
-
Okay, this is bizarre. Neither of those missions were actually altered. Which suggests this is actually a code issue.
-
But not everyone is having the problem, which means it's not easily-reproducible.
-
Docking works fine in mission 3 but I can't dock on the next mission. I've tried a new pilot file again on advanced difficulty but I can't dock at the end of mission 4.
I've attached a debug log if it's any help. I tried docking in the port dorsal bay but I've not tried the others yet and I'll also try lowering the difficulty.
[attachment deleted by an evil time traveler]
-
But not everyone is having the problem, which means it's not easily-reproducible.
Yeah, I'm pretty sure I couldn't land in the 1st mission under 1.0.4 once. But it worked OK after replaying the mission or restarting FSO (I forget which one it was).
-
Well this is exactly the sort of problem the event.log was designed to solve. Gimme a little bit, I'll upload a version of the mission that writes to the event log in an hour or two, as soon as I get back to my main PC.
EDIT : Okay you have three choices.
1) Run one of these missions until you can't land. Quit while you're still in a position you should be able to land.
2) Run a debug build. Get into a position where you should be able to land and then press ~ + Q. You Do not need to download a mission to do this.
3) Run a release build. Enter the cheat (www.freespace2.com IIRC). Get into a position where you should be able to land and then press ~ + Q. You Do not need to download a mission to do this.
Whichever you choose, I then need to get a look at the event.log you'll now have. It should tell me why the event isn't triggering.
NB. More details on 2 and 3 can be found here (http://www.hard-light.net/forums/index.php?topic=85174.0).
[attachment deleted by an evil time traveler]
-
Keep in mind landing code is different between Easy, Normal, and Advanced+ difficulties so please post which you've tested on.
-
The log should make it clear which path was followed, but it would be nice not to have to look through the log and figure it out. :)
-
Here you go, I've generated this by method 2 using the debug build on advanced difficulty for The Strike mission (SP-R1-M2.fs2). I think it was the starboard dorsal bay that I tried to land in but I don't think it worked in any of the other bays either.
[attachment deleted by an evil time traveler]
-
The log is a little hard to read cause you appear to have actually used method 1 and downloaded the missions I gave you. But I can quite clearly see that the Theseus has already departed when the log ends so I don't know when exactly you were supposedly in a position to land. Can you please quit while the Theseus is still present (or use the option in 2) and take a snapshot of the events as they are when you think you have landed.
Assuming that you were in the pod at the second the Theseus jumped out, you were not in the right position based on what the log states. The log states that at that precise time, you were stationary but 77m from the closest fighterbay subsystem. Since the game was on insane, you actually need to be within the box defined in the Landing event and the log states that at that time you were not. It is possible the box is slightly too big. Another possibility is that since the patch includes an altered MK 7 pof the centrepoint has moved and now the centre is outside the box even when landed. Although that seems unlikely given that the MK VIIe seems to also exhibit this issue.
-
Yeah I skim read the post so my mistake and I'll try again. Difficulty was set on medium before starting the mission not insane. I doubt this is relevant but I'm getting this during loading the mission.
Submodel <Seata> in model <Col_Viper_Mk7.pof> has a radius <= 0.1f
ntdll.dll! ZwWaitForSingleObject + 21 bytes
kernel32.dll! WaitForSingleObjectEx + 67 bytes
kernel32.dll! WaitForSingleObject + 18 bytes
fs2_open_Diaspora_R1_Debug.exe! <no symbol>
fs2_open_Diaspora_R1_Debug.exe! <no symbol>
fs2_open_Diaspora_R1_Debug.exe! <no symbol>
fs2_open_Diaspora_R1_Debug.exe! <no symbol>
fs2_open_Diaspora_R1_Debug.exe! <no symbol>
fs2_open_Diaspora_R1_Debug.exe! <no symbol>
fs2_open_Diaspora_R1_Debug.exe! <no symbol>
fs2_open_Diaspora_R1_Debug.exe! <no symbol>
fs2_open_Diaspora_R1_Debug.exe! <no symbol>
fs2_open_Diaspora_R1_Debug.exe! <no symbol>
fs2_open_Diaspora_R1_Debug.exe! <no symbol>
fs2_open_Diaspora_R1_Debug.exe! <no symbol>
fs2_open_Diaspora_R1_Debug.exe! <no symbol>
fs2_open_Diaspora_R1_Debug.exe! <no symbol>
fs2_open_Diaspora_R1_Debug.exe! <no symbol>
fs2_open_Diaspora_R1_Debug.exe! <no symbol>
fs2_open_Diaspora_R1_Debug.exe! <no symbol>
fs2_open_Diaspora_R1_Debug.exe! <no symbol>
fs2_open_Diaspora_R1_Debug.exe! <no symbol>
fs2_open_Diaspora_R1_Debug.exe! <no symbol>
kernel32.dll! BaseThreadInitThunk + 18 bytes
ntdll.dll! RtlInitializeExceptionChain + 99 bytes
ntdll.dll! RtlInitializeExceptionChain + 54 bytes
-
I've used method 1 this time which I've attached the log below. Again it is saying I'm playing at hard in the log when it is definitely set to medium (advanced) in the game options.
I've docked again in the starboard dorsal (upper right) bay. Just to check, if things were working as intended where do I need to be in the bay to dock successfully as I'm trying to dock in the middle? Should I be able to dock in any of the bays in this mission?
[attachment deleted by an evil time traveler]
-
Yeah, you should be able to dock in any of the bays.
The log is very helpful, for some reason, is-in-box is returning false, which means that either the box is too small, or the centre of the Viper has moved. Both of those shouldn't be too hard to test tomorrow.
-
Yeah, you should be able to dock in any of the bays.
The log is very helpful, for some reason, is-in-box is returning false, which means that either the box is too small, or the centre of the Viper has moved. Both of those shouldn't be too hard to test tomorrow.
In some of the missions I build the raptor wasn't able to land, just like the viper. So it's probably not the vipers' problem. I also played on normal difficulty.
I even increased the is-in-box size of the landing event (by changing the y values) but that didn't matter. Other is-in-box events did still worked properly.
I've reïnstalled diaspora to get an earlier version back to get rid of the issues.
There was another issue in Asheron mission 1 that caused the cargo carrier to continue moving, while it should have stopped. Now I've reïnstalled diaspora the cargo carrier does stop, while the mission file is unchanged..
-
I'm attaching a test mission. See if you can land in this version. You'll get a message when you do it successfully.
Cause it works perfectly for me. If it doesn't work, post the log again.
[attachment deleted by an evil time traveler]
-
Thanks Kara, seems to be working now. I tested (on medium difficulty) all the bays in the Mk7 successfully but then I remembered the landings were fine in mission 3 in the Mk7 so in FRED I switched the player to a Mk7e and the landing message still appeared!
-
So the test mission works but you still have problems with the real missions?
-
Yes, basically I can land okay in mission 3 (SP-R1-M1) and the test mission but I can't land in mission 4 (SP-R1-M2).
-
Sorry, was super busy. Replayed tutorial today, could land in tutorial 1 (automatic) and 2 (real combat landing).
Anything else I can do to help? Should I also follow your steps?
-
It would help. All that is necessary is to enter the cheat as soon as you notice you can't land and then take a snapshot of the SEXPs.
What difficulty level are you playing on?
-
Advanced, the 3rd of the five which is "Medium" in FS2. Will try to get that done tomorrow.
-
It only happens when I make the jump from Normal to Advanced. I can bounce along the flightpod runway as normal and not "collide", but my ship doesn't lock in place. Perfectly fine in the training missions, too. I'll check other missions to see if it works or not.
[EDIT] Okay, so far it's looking as though the issue is mission-specific. Played up to Desperation and I've had no issues with landing.
-
Okay, why are people who had problems before suddenly having no problems?
-
I wouldn't say I'm NOT having problems. The issue only exists in The Strike, which means there's an issue with the Mk VII-E model
-
Can you reproduce in the test mission I posted? Can you get me the event.log from a mission where you can't land please?
I really need these because I can't reproduce this myself in any mission. And people are reporting it in missions where you don't fly the MK VIIe.
-
I can tonight. You'll have results then.
-
Playing on advanced, first proper mission played in Debug build. Flushed at start of mission and multiple times after FTL came online. Tried to land in upper port bay, no success again. Event.log attached.
[attachment deleted by an evil time traveler]
-
This is bizarre, the is-in-box SEXP is returning false for some reason. Not sure why. Can you try the test mission I posted too?
-
Hi, devs! Thanks for the great BSG-game and new patch! But i find bug with TrackIR in 1.1
If i turn head - crosshair and LCOS move with eyesight, and i can't direct shoot! (sorry for bad english :))
add picture
(http://4.firepic.org/4/images/2014-02/17/vdfpdxlry9bm.jpg)
-
I vaguely remember hearing of a Track IR error in recent FS2_Open builds. Hopefully someone else remembers hearing about it.
-
I've confirmed it using "padlock" (since I don't have TrackIR) in a near current trunk bulid. The whole HUD seems to slew - I'm not sure what parts are not supposed to slew (except the reticle) and which are. I'll have to do some more digging to find which commit introduced this.
-
Same issue here - somewhere between R1 and R1.1, TrackIR stopped working effectively.
The reticle no longer stays where the guns are aiming, but rather follows the camera as your head moves using TrackIR. Means you can't identify where the real crosshair is, particularly because LCOS moves with the reticle.
-
This is bizarre, the is-in-box SEXP is returning false for some reason. Not sure why. Can you try the test mission I posted too?
My current run just ended with a nuclear shockwave while approaching the landing bay. Attached the event log anyway in case you can see something already but I repeat, I was not yet in the landing bay. That probably means another playthrough eh?
Has the build changed with the patch or something? I mean, you even said the mission has not changed and the sexps seem to be returning invalid values (on some machines). Maybe it is actually a code problem?
[attachment deleted by an evil time traveler]
-
Thing is that the SEXP works perfectly in the test mission I made. So I'm mystified as to why it wouldn't work in the real thing. I'll try altering the test mission to do the exact same thing the Theseus is doing at that point in the mission.
-
To the people who are having problem with the HUD reticle and TrackIR: could you please try this build (http://www.hard-light.net/forums/index.php?topic=86884.0) and let me know if it resolves the issue? Thanks
-
Hi niffiwan...just tried it out briefly and it appears to have worked. Thanks for the awesomely quick response!
-
No worries :D
(And I created the bug in the 1st place so... :nervous:)
-
This is bizarre, the is-in-box SEXP is returning false for some reason. Not sure why. Can you try the test mission I posted too?
Please give me some more detailed instructions again, do you want me to run the thing still or is the previous log sufficient?
-
There's a test mission in this post (http://www.hard-light.net/forums/index.php?topic=86565.msg1733834#msg1733834) which consists of just the landing SEXPs. Fly it and see if you can land. If you can't get me a snapshot. And a debug log too if possible.
-
To the people who are having problem with the HUD reticle and TrackIR: could you please try this build (http://www.hard-light.net/forums/index.php?topic=86884.0) and let me know if it resolves the issue? Thanks
It doesn't work for me. Neither does build 10475.
I believe you can test it without TrackIR by using the padlock panning thingy. It'd be great to get this bug squashed sometime soon so I could actually use the new mediaVPs and Diaspora 1.1.
-
Err... I did test it with padlock and it fixed the issue for me (& Yroethiel) :confused:
Could you post a screenshot of then issue? Or post a video? In addition to that, could you please post your fs2_open.log file. Instructions on how to do this can be found in this post.
-
http://i.imgur.com/eNppVjV.jpg
fs2_open.log
http://pastebin.com/8VXvxQbL
Tried 10462 with FS2 Titan Rebellion and no go.
-
http://i.imgur.com/eNppVjV.jpg
fs2_open.log
http://pastebin.com/8VXvxQbL
Tried 10462 with FS2 Titan Rebellion and no go.
Thanks - I found that I'd missed the Diaspora Lead Sight gauge from my fix (silly me didn't test Diaspora previously, only FS2).
For FS2 + Titan Rebellion though, I thought I'd got all the gauges, could you grab a screenshot with that not working correctly so I can see what's going on?
-
I'm sorry, FS2 actually works fine when I disabled cockpit mod. This one: http://www.hard-light.net/forums/index.php?topic=84459.0
It uses similar targeting reticle system like in Diaspora. If you can fix the diaspora one then both will propably work?
-
ah yes - that makes sense. I committed the fix locally last night but it seems I forgot to push it to SVN, I'll do that tonight hopefully before the next nightly build is created.
-
Works nicely now with both Diaspora and FS2 TitanR.
-
Hurrah, and thanks for testing :yes:
-
Alright...
I got 1.0.4 patch running.
This one is 1.1
Is this a working thing? I see a lot of issues posted here, and it is not clear to me if I should Patch it up to 1.1, or that I shouldn't because it isn't working and I have to do a lot of homework/reading stuff to get it to work as it should.
No guarantees I understand, but if it is working for some whithout any problems/retinkering whatsoever, it would help if they posted too.
Maybe a thread: "Is it working for you without problems..post here" ?
:)
-
A lot of people seem to be complaining about the landing issue but I still can't figure out why. I intend to get to the bottom of the issue this week.
-
A lot of people seem to be complaining about the landing issue but I still can't figure out why.
I can confirm that the bug also happens in your landing test mission here, I am seeing "Command Land" but my Viper does not lock to the ground.
-
Now that's interesting. I can't reproduce that on my machine but the fact it happens on yours does rule out some possible issues.
EDIT : Nevermind, I forgot that I didn't add the locking stuff to the test mission. If you're getting the landed message in the test, you have actually triggered the event. Which isn't what is happening in the missions apparently.
-
any more instructions?
-
It appears to be a code issue. The is-in-box SEXP isn't triggering when it really should be. Unfortunately my vector maths isn't up to figuring out why.
-
Can you please release a platform-agnostic .zip of the updated VPs or whatever rather than just a Windows-only installer?
-
I was expecting the others to be uploaded but I think we got bogged down with the "Can't land" issue so no one has created the Linux or Mac Versions yet.
I'll get a zip of the files up later today.
-
Yeah I prised the Windows patch apart with Wine and I ran into the landing bug. You said it was a code problem earlier, does that mean it's not fixable with these patches?
-
The landing bug was introduced in 1.1.
-
Can you please release a platform-agnostic .zip of the updated VPs or whatever rather than just a Windows-only installer?
I'm holding off releasing a packaged Mac version until we resolve the SEXP landing bug.
-
I posted a build on this thread which I suspect solves the bug (I simply reverted Goober's fixes to the is-in-box SEXP) but I haven't received any feedback yet. If someone could please test the builds that would help a lot.
-
Can you please release a platform-agnostic .zip of the updated VPs or whatever rather than just a Windows-only installer?
Well, there's always this:
Since nobody else has done it yet:
http://deviance.duckish.net/downloads/Diaspora_1.1.7z
-
I posted a build on this thread which I suspect solves the bug (I simply reverted Goober's fixes to the is-in-box SEXP) but I haven't received any feedback yet. If someone could please test the builds that would help a lot.
Just tested with the above 7z patch file and I can now dock on the mission (advanced difficulty) I was stuck on.
-
That's really weird considering it was a code issue.
-
How would it be weird? He just tested the reverted-code version which fixed the issue.
-
That's really weird considering it was a code issue.
I assume he means the 7zip of the build not the 7zip of the game.
-
To be clear I installed the R1 release from the windows installer and then patched to 1.1 with the Diaspora_1.1.7z.
-
You didn't use the exe files from the other thread?
It's possible you just got lucky.
-
Sorry if I'm being thick but which thread are you refering to? I can try again after work and see if it has been solved.
-
Hmmm. It appears that I didn't include the link earlier.
Can everyone experiencing issues on Windows please try using these builds (http://fs2downloads.com/Misc-Downloads/Builds/Landing_Test_Builds.7z) with patch 1.1.
-
I reinstalled with the Windows installers and using the builds it seems to be working perfectly now. So far I've docked without any problems up to the end of the fourth mission, Distress.
-
Works for me, R1.1 combined with the FS2 open 3.7.1 you posted, has the same landing behaviour as 1.0.4
-
Hello.
I have no idea what to do with both the
fs2_open_3_7_1.exe
fs2_open_3_7_1-DEBUG.exe
or in what folder I must have them.
If I exe them I get black screens. And when I panic and CTR+ALT+DEL this proces I get big lettered screens claiming errors, and having modified freespace, or not running it at all.
What do I have to do with these two files? How exactley does this work?
What are debug executables for? Do I need to start these or the other one? A help.txt might help a lot of us noobies out here :P
*left in the dark* *panic..* (and then you feel really glad you just put down temporarilly all your antivirus shielding for troubleless installations..... :( ) :banghead: :banghead:
-
Put both the files in your Diaspora folder. You normally use this one (fs2_open_3_7_1.exe) unless someone asks for a debug log, in which case run the other one.
-
ok.
And do I need to execute it, or does Dia do that itself?
-
fs2_open_Diaspora_R1.exe
is there too. does it need to remain there too?
they got the same icon, so this confuses me into thinking they (should) replace one another..
-
You should have both fs2_open_Diaspora_R1.exe and fs2_open_3_7_1.exe in the Diaspora folder at the same time. They do the same thing so in theory they could replace each other, but given that this is a test executable, not an official release, I would keep both.
You should be able to either run fs2_open_3_7_1.exe directly, or you can select it as the executable in the Launcher and run it that way.
-
I've posted some new builds that should work. You can find them here (http://www.hard-light.net/forums/index.php?topic=87201.new#new).