OpenSauce Halo CE SDK Update #2 (RC)

[ShadowSpartan]

Radiosity was an example of how I could swap lightmaps and then recompile the map. I didn't mean it as something to be confusing.

Korn wasn't confused, he understood what you were talking about. You are the one that is confused. Changing the lightmap tag reference and recompiling the map is not the same as changing it at runtime (while the game is running). Read the very beginning of FireScythe's post, he explains why it more than likely won't be as simple as changing a tag reference.

[Rambo]

OK. It still should work, in theory. You aren't rerunning radiosity each time, just changing the tag. If recompiling it makes it work, on-the-fly lightmap switching should work in the same way switching BSPs on the fly works.

I'd do it, but I don't know XML or any programming language. I'm just a sound man and script in Halo some.

[ShadowSpartan]

OK. It still should work, in theory. You aren't rerunning radiosity each time, just changing the tag. If recompiling it makes it work, on-the-fly lightmap switching should work in the same way switching BSPs on the fly works.

No. There is no guarantee that changing the tag reference while the game is running will force the lightmaps to change. That would imply that the lightmap tag reference field is constantly being checked for any changes, which it is not. There would be no point in monitoring if the tag reference changes, especially since the lightmap cannot normally be changed at run time. Use common sense.

This would not have the same effect as the "switch_bsp" command. When you switch a bsp using that command, the new sbsp tag is loaded, as well as all of it's dependents. One of the dependents is it's corresponding lightmap tag. You have no idea what you are talking about, so please stop.

I'd do it, but I don't know XML or any programming language. I'm just a sound man and script in Halo some.

Damn Korn, you should have written OS in nothing but XML. I think I'll do that for my next app.

[TVTyrant]

E:B;eh one second.
So where do I find exception data?

[ShadowSpartan]

XP:

On XP, I believe there is a way to save the Exception Data of which it notoriously Gathers. Try clicking the "View Details" linkish looking thing (IIRC) and see if it lets you.

On Vista its a little different. This difference actually made developing hacks like Yelo more time consuming to debug on my end as the amount of steps involved.
1) Control Panel->Problem Reports and Solutions->View problem history
2) Find HaloCE (or it may be the name of the dll, dx3d9.dll or w/e)
3) Right click->View problem details.
4) Copy to clipboard & pasta in your post
5) ???
6) Fix?
7) Deficit

Vista:
Start>Control Panel>System and Maintenance>Problem Reports and Solutions>Find Halo report at specific date/time and copy to clipboard

W7:
Start>Search for "View all problem reports">Find Halo report at specific date/time and copy to clipboard

[TVTyrant]

Product
Halo

Problem
Stopped working

Date
9/8/2009 2:02 PM

Status
Report Sent

Problem signature
Problem Event Name: APPCRASH
Application Name: haloce.exe
Application Version: 1.0.8.616
Application Timestamp: 489a3b7e
Fault Module Name: d3d9.dll
Fault Module Version: 2.0.0.1
Fault Module Timestamp: 4a984fec
Exception Code: c0000005
Exception Offset: 00016686
OS Version: 6.0.6001.2.1.0.768.3
Locale ID: 1033

Extra information about the problem
Bucket ID: 1439092421

That stuff?

[ShadowSpartan]

That stuff?

Yes, that is correct.