Project Reality Forums

Well, I've walked in to qinling and kashan and noticed the clouds being seperate effects, is there easy way to do this or do you have to place em all manually?

Thanks

***********************solved*****************************

Map Crashes on Objects at 14%, what is the problem? Is it certain statics?

Thanks

^^^

easyist way, copy and paste the from one staticobjects.con to anouther.

[R-DEV]Rhino wrote:easyist way, copy and paste the from one staticobjects.con to anouther.

Ah, it would be a little more trickier for 8x8

Ok so we just copy and paste the one with the coordinates (on the buttom) and not the top one with the run/objects....so on.

8x8? what are you planing?

nothing in particular.....

Lol wow yes I know. Thanks for the help anyway?

Question updated....

No erroer, And I think there is some kits that I put in to spawn (like the .50 cal you mean right?)

I'll delete em.

8x8 km ´maps arent possible, am i right???

J.F.Leusch69 wrote:8x8 km ´maps arent possible, am i right???

even 16x16 maps are possible, hell i bet 32x32, but there is limits to where you can texture, etc.

Jonny wrote:That sounds like a problem with spawn kits, check the init.con

Is there an error? If not it really does sound like the kits are non existant editor added ones, or the game looking for non existant weapons.

At least I dont remember getting that sort of CTD any other way that you could have done.

I checked the init with the pr guidelines, still no work.

I don't have anykits that spawn in...just objects for testing.

Im mad

BUMP

Map Crashes on Objects at 14%, what is the problem? Is it certain statics?

halp

oh, and I've searched bf editor forums, and when ever I search ANYTHING the same exact results come up, or that it can't find anything. ??:

What does the dump file tell you about the error?

If nothing, try starting the game in windowed mode and see if it tells you anything in the dump.

If that doesn't work, start the debugger, prepare to click your mouse a thousand times , and click through the CTD.

That should give you the error in question in the dump file.

What does the dump file tell you about the error?

What do you mean?

If nothing, try starting the game in windowed mode and see if it tells you anything in the dump.

No error is prompted

If that doesn't work, start the debugger, prepare to click your mouse a thousand times , and click through the CTD.

how do we do that exactly?

That should give you the error in question in the dump file.

I had this very same problem, CTD at 14 percent. Check your Init.con and make sure the kit loadout is correct.

Example:

gameLogic.setTeamName 1 "MEInsurgent"
gameLogic.setTeamName 2 "US"

gameLogic.setTeamLanguage 1 "MEC"
gameLogic.setTeamLanguage 2 "English"

gameLogic.setTeamFlag 0 "flag_neutral"
gameLogic.setTeamFlag 1 "flag_in"
gameLogic.setTeamFlag 2 "flag_us"

gameLogic.setKit 1 0 "meinsurgent_officer" "meinsurgent_soldier"
gameLogic.setKit 2 0 "us_officer" "us_heavywhite_soldier"

gameLogic.setKit 1 1 "meinsurgent_insurgent" "meinsurgent_soldier"
gameLogic.setKit 2 1 "us_riflemanab" "us_heavywhite_soldier"

gameLogic.setKit 1 2 "meinsurgent_ambusher" "meinsurgent_heavy_soldier"
gameLogic.setKit 2 2 "us_rifleman" "us_heavy_soldier"

gameLogic.setKit 1 3 "meinsurgent_warveteran" "meinsurgent_medium_soldier"
gameLogic.setKit 2 3 "us_medic" "us_lightarmor_soldier"

gameLogic.setKit 1 4 "meinsurgent_civilian" "meinsurgent_soldier"
gameLogic.setKit 2 4 "us_engineer" "us_heavywhite_soldier"

Basically, all of the basic kit spawns as you would see in-game. Rhino's threads here (https://www.realitymod.com/forum/f189-m ... audit.html) had different kit loadouts, and that could affect the loading process. My old map had to be scrapped and I started new. Adjusted kit loadout, loads fine.

*slaps forehead* didn't I say this was not the problem? Well if i didn't say, that is not the problem. and I have read rhinos tuts almost fully and important parts like those I did not miss. thanks but no thanks

It seems like you are getting into editing so i will tell you how to at least try and read the CTDs yourself.

Anytime the game CTDs, it gives a dump file.
Sometimes this file will give you the reason it crashed.

My Documents\Battlefield 2\dmp is where my dump files are stored.
Yours should be in a similar location.

Opening these files to read is a different story.
Wordpad and Notepad just give us garble.

So, download and install the debugging tool from the link below...choose the 32 bit or 64 bit depending on your OS.

Install Debugging Tools for Windows 32-bit Version

(FYI, once it is installed, create a shortcut for it and put it on your desktop for easier access to start it up)

Once installed, start the program, follow the path below in the pic and then choose the folder where dumps are located.

Once there you will see the dump files that have been created.

Choose the most recent dump file!

1) In general when the game runs in full screen and CTDs, the dump file will give you no info on why.
Dump files that contain no info to your problem will look like this.



Dump files that actually give you the reason will look more like this.

The part I have highlighted in red is the only thing that matters.
The other stuff is junk.
My CTD was because of a weapon index conflict with hgr_smoke in a GB kit.

2) Another way of getting the game to tell you why it CTD is to play the game in windowed mode (non-full screen).
Generally if it crashes in windowed mode, an error window will pop up right after the crash and will tell you why.
You can stop there and right down what is says OR you can again just open the dump file that was created and it will have the same info as the pop screen.

3) Running in debug mode is when the dumps tells you nothing even in windowed mode.
It's located in the main BF2 folder usually...Program Files\EA GAMES\Battlefield 2
It's the icon that says BF2_r.exe

Start it up and prepare to click continue a thousand times to get to your error.
You know the game is crashing at around 14%, so keep clicking 'CONTINUE' until you pass that.
Everytime you say continue and the game doesn't crash, the error that popped up is not your problem.
Your problem will be the one that makes the game actually CTDs again.
Once this happens, check the dump files again.

It should give you a reason.

BTW, sorry this was so long...i had a link to tut that explained this all, but I don't have it anymore.

HughJass wrote:even 16x16 maps are possible, hell i bet 32x32, but there is limits to where you can texture, etc.

How?

ballard_44 wrote:It seems like you are getting into editing so i will tell you how to at least try and read the CTDs yourself.

Anytime the game CTDs, it gives a dump file.
Sometimes this file will give you the reason it crashed.

My Documents\Battlefield 2\dmp is where my dump files are stored.
Yours should be in a similar location.

Opening these files to read is a different story.
Wordpad and Notepad just give us garble.

So, download and install the debugging tool from the link below...choose the 32 bit or 64 bit depending on your OS.

Install Debugging Tools for Windows 32-bit Version

(FYI, once it is installed, create a shortcut for it and put it on your desktop for easier access to start it up)

Once installed, start the program, follow the path below in the pic and then choose the folder where dumps are located.

Once there you will see the dump files that have been created.

Choose the most recent dump file!

1) In general when the game runs in full screen and CTDs, the dump file will give you no info on why.
Dump files that contain no info to your problem will look like this.



Dump files that actually give you the reason will look more like this.

The part I have highlighted in red is the only thing that matters.
The other stuff is junk.
My CTD was because of a weapon index conflict with hgr_smoke in a GB kit.

2) Another way of getting the game to tell you why it CTD is to play the game in windowed mode (non-full screen).
Generally if it crashes in windowed mode, an error window will pop up right after the crash and will tell you why.
You can stop there and right down what is says OR you can again just open the dump file that was created and it will have the same info as the pop screen.

3) Running in debug mode is when the dumps tells you nothing even in windowed mode.
It's located in the main BF2 folder usually...Program Files\EA GAMES\Battlefield 2
It's the icon that says BF2_r.exe

Start it up and prepare to click continue a thousand times to get to your error.
You know the game is crashing at around 14%, so keep clicking 'CONTINUE' until you pass that.
Everytime you say continue and the game doesn't crash, the error that popped up is not your problem.
Your problem will be the one that makes the game actually CTDs again.
Once this happens, check the dump files again.

It should give you a reason.

BTW, sorry this was so long...i had a link to tut that explained this all, but I don't have it anymore.

thanks a lot man, looks like im going to have to use method 3. Ill get back to you. once agian thanks!

Oh and tonnie dont hijack the thread...



edit:

bf2_r does not work ... it says im missing VtuneApi.dll