[Bobboau]

try a debug build!
http://freespace.volitionwatch.com/blackwater/fs2_open_d.zip

[Omniscaper]

The debugger keeps looking for stuff on a drive  I:  ?

[Bobboau]

no it isn't looking for anything it's telling you were I keep my source code, that's a standard error message,
...probly...

what's it say?

[Omniscaper]

Warning: cannot find bitmap nebulA1-main
File:I:\FSO\fs2_open\code\Starfield\StarField.cpp
Line: 811

Call stack:
------------------------------------------------------------------
    game_init()    WinMainSub()    WinMain()    WinMainCRTStartup()    kernel32.dll 7c816d4f()
------------------------------------------------------------------




I get a number of these till i get inside the game. The moment I go to the techroom the killer error that drops to desktop:


Assert: bay->num_slots == 2
File: I:\FSO\fs2_open\code\Model\ModelRead.cpp
Line: 2148

Call stack:
------------------------------------------------------------------
    model_load()    techroom_select_new_entry()    techroom_change_tab()    techroom_init()    game_enter_state()    gameseq_set_state()    game_process_event()    gameseq_process_events()    WinMainSub()    WinMain()    WinMainCRTStartup()    kernel32.dll 7c816d4f()
------------------------------------------------------------------
:

[Bobboau]

ok, that first one means that it can't find the texture
nebulA1-main
it is a background nebula image (as opposed to a sun or a planet), look in your active stars table, and make sure the file is spelled the same way and in the right folder.

the second one, the model it's trying to load, it has a dock, with only one point, all docks must have exactly two points.

[Omniscaper]

I'm sorry, I don't mean to make this threa my personal troubleshooting topic... after fixing MANY tbl errors what not... this one, I am dumbfounded.

Assert: f < MAX_MEM_POINTERS
File: i:\fso\fs2_open\code\globalincs\windebug.cpp
Line: 1489

Call stack:
------------------------------------------------------------------
    vm_free()    close_help()    doexit()    exit()    WinAssert()    unregister_malloc()    vm_free()    close_help()    doexit()    exit()    WinAssert()    unregister_malloc()    vm_free()    close_help()    doexit()------------------------------------------------------------------

[Bobboau]

that's an unpleasent looking fellow...

were the hell did that show up?
I hope it was when you hit cancel on an Assert or something.

[Omniscaper]

Thats the first message as soon as I load a simple Viper vs Cylon mission.

This is the following message.

Assert: TotalRam == total
File: i:\fso\fs2_open\code\globalincs\windebug.cpp
Line: 1443

Call stack:
------------------------------------------------------------------
    doexit()    exit()    WinAssert()    unregister_malloc()    vm_free()    defpoint()    parse_bsp()    initalise()    ship_create()    parse_create_object()    parse_object()    parse_objects()    parse_mission()    parse_main()    mission_load()------------------------------------------------------------------

[Bobboau]

that means there is something realy weired up with the memory tracker, wich is bad, hmmm...

oh well, too late for me to do anything about it now, just late enough for me to go to sleep though

[Drew]

that debug dont work for me either crashes when i commit

[Omniscaper]

Thank you anyway. You dedication kicks ass as it is.

[DaBrain]

Yay I got a mission working! But only for a few seconds
(I think it crashed as soon as I moved the joystick)

But I found a bug.


The weapon effects look kinda wrong.

http://img169.exs.cx/img169/7558/screen00673wj.jpg

[MetalDestroyer]

Wow , i 'm impressed, it's definitively excellent for Star Trek and SW universe

[DaBrain]

Ok, I've tried the warp build.
It has the same bug but it works.


Here are some more bugs:

Satanas jumping out. Looks retro
http://img208.exs.cx/img208/5269/warp3wo.jpg (BTW I'm using the EFF warp effect.)


And the thruster code seems to need some tweaking.

http://img208.exs.cx/img208/5932/thurster12ro.jpg

http://img208.exs.cx/img208/4594/thruster23jv.jpg

http://img208.exs.cx/img208/2464/thruster33mc.jpg

(The second one looks quite cool somehow. Like beam effect.

[Dark RevenantX]

engine trails...

[Gregster2k]

I use OpenGL and the fighter-explosion Boom build CTD's when I push the COMMIT button on any mission.

As for the standard Warpball one (3-16-05) -- -the effect does not look like your screenshots whatsoever...it is a static ray-ball that expands and contracts JUST AFTER the main warp funnel shrinks to nothingness.

Unless that's what you wanted. But it doesn't look "right" to me. It looks the same in D3D...main funnel shrinks to nothing and secondary rayball suddenly expands and then disappears.

EDIT: Just a moment, I just realized that the screenshots on Page 1 were taken from a much further distance than i have been viewing subspaces here...ill go check. BTW: I'm also using that enhanced EFF warp effect.

EDIT 2: Yeah, it still looks the same, any distance. It does not look anywhere NEAR what those screenshots look like in coolness.

[DaBrain]

Bob's builds are more or less D3D only....

[Gregster2k]

DaBrain: I checked it in D3D: It looks just as bad on my system. It simply looks like a 2D blast flare effect sizes up and down, there's none of this directional flaring I see in the screenshots.

I like the effect, but it is apparently not cross-system compatible...

[Jetmech Jr.]

This ****ing rocks.

[FireCrack]

I also have the problem where it only flares up when the warp hole closes, but i think that looks friggin awesome because the warphole closes and then you just see this big flash. Same for opening.

You guys should try this in OGL, especialy bob, it looks very cool IMO.