103 replies to this topic

[VK]

NP SE Bugs/errors feedback thread

[Gaffel]

I got a random IE with NPSE. It happend when I played online with my broder and when a unit was built. I tried again to build that unit but no IE appeared. I never have this problem before with NP 1.00
 except.txt   26.16KB   210 downloads

[VK]

Will be handled.

[Blade]

I get this error every time I try and exit the game if I save it at any point (including auto save from campaigns). This has persisted for since saves were fixed in RPCE. Error only occurs as the game exits but its annoying since I need to alt+tab to finish closing the game down.

Attached Files

•  except.zip   4.89KB   138 downloads

[SSTG]

Is that advancepower= tag still in effect just checking cause I wanna see if this IE I'm getting is caused by it

[tmapm]

Error: UseNewMainMenu is default to 'yes'
Version: NPatch SE - 1.05

[VK]

Error: UseNewMainMenu is default to 'yes'
Version: NPatch SE - 1.05

this isn't a bug.
I designed it so

Is that advancepower= tag still in effect just checking cause I wanna see if this IE I'm getting is caused by it

no.

[tmapm]

For an add-on patch, it is illogical to have new features enabled by default. With non-modified rules, the game should function as if the patch was not installed.

[Blade]

I agree, I thought it strange when I first ran the game with the new patch. Same thing goes with the menu for mission selection that is enabled by default when it isn't in the normal game.

[DonutArnold]

Aircraft dies when they shoot a target, do you know what couses this?

[VK]

For an add-on patch, it is illogical to have new features enabled by default. With non-modified rules, the game should function as if the patch was not installed

I agree, I thought it strange when I first ran the game with the new patch. Same thing goes with the menu for mission selection that is enabled by default when it isn't in the normal game.

no. I consider NPatch not as small-facking-no-CD-crack, but as BIG extension for YR Engine.

NPatch (now) still have compatible mode with YR 1.001, but this don't mean that it must look like orginal YR 1.001. and it won't in future.

[tmapm]

From the manual:

If you want use this feature, put UseNewMainMenu=yes to UISettings section.

I don't want to use the feature, so why should I have to use it to not use it? It doesn't make sense to have the default set to "yes".

Edited by tmapm, 28 August 2007 - 09:41 PM.

[VK]

I don't want to use the feature, so why should I have to use it to not use it? It doesn't make sense to have the default set to "yes".

this just error in documentation.
I usually update documentation later, after first final revision.
So it sometimes have errors. (like in the nearest thread)

[Vinifera7]

It makes no sense to have a new modding features be enabled by default.

With non-modified rules, the patched game should be exactly the same as the unpatched game. That way, people can play regular YR or any mods without having to uninstall the patch.

I would think that NPatch should be treated as an exe patch that adds extra modding capability, not as a mod in itself.

[VK]

I would think that NPatch should be treated as an exe patch that adds extra modding capability, not as a mod in itself.

no NPatch should be treated a new engine, based on YR engine.
(NPatch features extend YR engine for modding in times)

With non-modified rules, the patched game should be exactly the same as the unpatched game. That way, people can play regular YR or any mods without having to uninstall the patch.

who say this?
forgot about it
probably the next NPatch version (NPAE) will be the last NPatch applied to GAMEMD.EXE; then it will use separate stuffs like GAMENP.EXE. It can be no longer compatible with original YR at all.

[Blade]

I don't agree that it is a good idea to loose backward compatibility with the original rulesmd.ini, where ever possible I think you should strive to set default values for new tags such that they match the original behaviour. It also makes developing a mod a much easier prospect when you have a known base to work from that you know will work a certain way.

[VK]

I don't agree that it is a good idea to loose backward compatibility with the original rulesmd.ini, where ever possible I think you should strive to set default values for new tags such that they match the original behaviour. It also makes developing a mod a much easier prospect when you have a known base to work from that you know will work a certain way.

however this is good solution.
You will run GAMEMD.EXE for original YR mods and for RP/old NP mods.
And you will run GAMENP.EXE for new NPatch mods.
this is really good idea.

Yes some tools, like XCC Mod Launcher will become obsolete, but new multi-mod system will solve it

[Blade]

I'm sure mod launcher can be recoded to run the new exec without too much trouble, but my point remains, any mods will be built off a base rulesmd.ini so your patch should play the default game without problems.

[Mig Eater]

There is no point arguing with him about it, it’s his project & he can do whatever he likes with it.

[Blade]

From the title, this looks like a feedback thread and I'm giving feedback. The problem his plan has is installing the NPatch on its own will do nothing except give an extra icon to click that will had random IE's and will looks strangely different (and IMO lower quality, the old select screen looks tacky). The menu system doesn't even stay consistent, it just changes after that first screen. People will blame the patch for being buggy when really its just that the defaults for some tags will be set (from the point of view of unmodded YR) wrongly. This wouldn't be a problem if it was combined with UMP to make an unofficial patch that fixed bugs as well as settings the tags correctly for default behaviour, but it isn't.