Hard Light Productions Forums
Modding, Mission Design, and Coding => The FRED Workshop => Topic started by: woutersmits on October 14, 2016, 04:22:20 am
-
its hes 1 bug with fighter wing capicorn it stands 0 it needs to be 1
on mission 4
Arrival distance for wing Capricorn cannot be 0. Setting to 1.
KERNELBASE.dll! WaitForSingleObjectEx + 268 bytes
KERNELBASE.dll! WaitForSingleObject + 18 bytes
fs2_open_3_7_2-DEBUG.exe! SCP_DumpStack + 354 bytes
fs2_open_3_7_2-DEBUG.exe! Warning + 421 bytes
fs2_open_3_7_2-DEBUG.exe! parse_wing + 872 bytes
fs2_open_3_7_2-DEBUG.exe! parse_wings + 114 bytes
fs2_open_3_7_2-DEBUG.exe! parse_mission + 509 bytes
fs2_open_3_7_2-DEBUG.exe! parse_main + 444 bytes
fs2_open_3_7_2-DEBUG.exe! mission_load + 228 bytes
fs2_open_3_7_2-DEBUG.exe! game_start_mission + 192 bytes
fs2_open_3_7_2-DEBUG.exe! game_enter_state + 511 bytes
fs2_open_3_7_2-DEBUG.exe! gameseq_set_state + 310 bytes
fs2_open_3_7_2-DEBUG.exe! game_process_event + 242 bytes
fs2_open_3_7_2-DEBUG.exe! gameseq_process_events + 152 bytes
fs2_open_3_7_2-DEBUG.exe! game_main + 782 bytes
fs2_open_3_7_2-DEBUG.exe! WinMain + 330 bytes
fs2_open_3_7_2-DEBUG.exe! __tmainCRTStartup + 358 bytes
fs2_open_3_7_2-DEBUG.exe! WinMainCRTStartup + 15 bytes
KERNEL32.DLL! BaseThreadInitThunk + 36 bytes
ntdll.dll! RtlSubscribeWnfStateChangeNotification + 1081 bytes
ntdll.dll! RtlSubscribeWnfStateChangeNotification + 1028 bytes
thats all here's log and campaign
https://1drv.ms/u/s!Anh2Q9xPqybigZd59GdH4q-6cUlKAA
[attachment deleted by admin]
-
This can be fixed in FRED... It is a "Near Ship" arrival flag.
-
btw who builded this
-
btw who builded this
Where did you download it from?
-
it didnt
my pc created out of nowhere
-
I guess you answered your own question then.
-
Why not post it then? That way we can praise its immaculate mission design.
-
Reasen is its not finished becouse at the end something about supernova
Cappela no credits afther all
Even afther its nothing
-
Conflict Zone is my first released campaign, I wasn't having the issue you mentioned, but thanks for reporting it. Currently I am not able to further look into the problem, but I will when able.