Sorry your browser is not supported!

You are using an outdated browser that does not support modern web technologies, in order to use this site please update to a new browser.

Browsers supported include Chrome, FireFox, Safari, Opera, Internet Explorer 10+ or Microsoft Edge.

FPSC Classic Scripts / Menu Script Problem?

Author
Message
ArcGames
14
Years of Service
User Offline
Joined: 26th Jul 2010
Location:
Posted: 1st Aug 2010 00:22 Edited at: 1st Aug 2010 00:23
I took and modified the titlepage.fpi to create two menus, one is the Main Menu the other is an Options Menu, both in the titlepage.fpi Please excuse the graphics as I will not be using them, they are for testing purposes.

The problem I am getting is, mouse trails all over the place, see the images below. Also I have included my titlespage.fpi script. Please help me, tell me how I can get rid of the mouse trails?





Plystire
21
Years of Service
User Offline
Joined: 18th Feb 2003
Location: Staring into the digital ether
Posted: 1st Aug 2010 04:39
Why are you making two different pointers in your script? There should only be one pointer created. Just use the original pointer for whatever it is you need.


The one and only,


ArcGames
14
Years of Service
User Offline
Joined: 26th Jul 2010
Location:
Posted: 1st Aug 2010 05:42 Edited at: 1st Aug 2010 05:48
If you remove the second pointer, the cursor will not appear on the OPTIONS SCREEN, or if you remove the first pointer the cursor will not appear on the MAIN MENU screen. So both pointers have to be there. I know, I have tried it both ways. You can remove one of the pointers and make it show, but it will be behind everything on the OPTIONS MENU.

No matter what, the mouse trails are still there. It is not because of two pointers. So how do I get rid of the mouse trails, any ideas?

Test this out for yourself and you will see!
ctm
19
Years of Service
User Offline
Joined: 25th Feb 2005
Location:
Posted: 1st Aug 2010 10:05
Put the hud setups in state=6 to the state=0 field above the original pointer setup and the problem should be gone.

ArcGames
14
Years of Service
User Offline
Joined: 26th Jul 2010
Location:
Posted: 1st Aug 2010 10:38
@ctm No that doesn't work, all that does is cause the second menu from showing. Any other ideas?
ctm
19
Years of Service
User Offline
Joined: 25th Feb 2005
Location:
Posted: 1st Aug 2010 12:52 Edited at: 1st Aug 2010 14:48
Arg, sorry i made a mistake in the code i posted. Forgot to change state=6 to state=0 in the 2 lines which set up the HUDs:



If the menu still does not show up it's maybe necessary to run the state=0 part again for a hudreset:



If this also does not work the question arises if it's possible at all in the titlepage.fpi.
I am pretty sure it's possible in the setuplevel.fpi
ctm
19
Years of Service
User Offline
Joined: 25th Feb 2005
Location:
Posted: 1st Aug 2010 19:10
I made some tests and the result is that it's not possible to make a submenu in the titlepage.fpi because FPSC is to fussy about how to use the hud actions in this fpi.

It does'nt like it when you use the hudhide=1 action.
Whenever it's used it smears the pointer over the screen.

But you cannot make a submenu without using this action.

That's the original fpi:


And my edited version for the test:
Plystire
21
Years of Service
User Offline
Joined: 18th Feb 2003
Location: Staring into the digital ether
Posted: 1st Aug 2010 21:23
Well if it's only "hudhide" that it has a problem with, then can't you not use "hudhide" and instead use "hudunshow" immediately after creating the HUD?


The one and only,


ctm
19
Years of Service
User Offline
Joined: 25th Feb 2005
Location:
Posted: 2nd Aug 2010 02:32 Edited at: 2nd Aug 2010 02:58
Good idea.
But i will not test it because...to be honest i don't see a practical purpose to make a sub menu in the titlepage.fpi unless you tell me that there is a chance to change the setup.fpi settings there

All ingame stuff can be done in the setuplevel.fpi

Edit:
Jumped out of my bed and booted pc again because i remembered that i have tested hudmake->hudunshow...didnt work.
I made 30+ tests this afternoon...best result was no smearing in the main menu but always smearing in the submenu.

And ...ok, there could be a praktical use...something like difficulty settings etc.
Maybe someone else finds a solution...me'll go to bed now...again
Plystire
21
Years of Service
User Offline
Joined: 18th Feb 2003
Location: Staring into the digital ether
Posted: 2nd Aug 2010 06:45
Darn... well it was worth a shot at least, right?

How about redirecting the script to another script (that will run the submenu) via "runfpi"?

I honestly can't test any of these theories out since I'm not on my FPSC comp.


The one and only,


ctm
19
Years of Service
User Offline
Joined: 25th Feb 2005
Location:
Posted: 2nd Aug 2010 13:49
I tried runfpi=X (accordingly to the example in the ocfpsguide) without success.

Submenu script does'nt start and titlepage.fpi stops when the action is called.

Here is a version (for everyone who is interested) which shows the pointer normal in the main menu and smearing in the submenu.

Testing is realy easy because i only used button.tgas which are already there.
The only thing you need is a already build testgame. Just replace the titlepage.fpi with this version.

Login to post a reply

Server time is: 2024-11-24 21:54:49
Your offset time is: 2024-11-24 21:54:49