PyWright Case Engine ver 0.9880! (Finally) : Games

Re: The PyWright Casemaker Thread - beta 10.7 (nov30)

Thu Dec 04, 2008 7:57 am

saluk

Gender: Male

Rank: Prosecutor

Joined: Thu Mar 06, 2008 8:36 pm

Posts: 770

Well, not enough for 10.8, but 10.71 is live. Fixes the minor reported issues. Makes editor a little more usable. Still a joke, but somewhat usable.

Creator of PyWright, the lovable case construction system!
Also visit the PyWright post.

Re: The PyWright Casemaker Thread - beta 10.7 (nov30)

Thu Dec 04, 2008 9:40 am

Reiji_kun

Xin Eohp.png

Gender: None specified

Rank: Suspect

Joined: Sat Nov 22, 2008 6:43 am

Posts: 5

How do you use PyWright? I'm still pretty new to this so... :meekins:

Re: The PyWright Casemaker Thread - beta 10.7 (nov30)

Thu Dec 04, 2008 5:18 pm

saluk

Gender: Male

Rank: Prosecutor

Joined: Thu Mar 06, 2008 8:36 pm

Posts: 770

-Use the updater to download characters you need for your case.
-Also download the test games, these will be useful to learn from
-Play some of the test games and look at the code to get a feel for it
-If you are making one case only, make a new folder under games with the name of your case.
-If you are making a collection of cases, make a new folder under games with the name of your game, and then a new folder inside your game folder with the name of the first case you are working on.
-Make a new file inside the case folder called intro.txt (games/mycase/intro.txt or games/mygame/mycase/intro.txt)
-Start writing your case in there, whenever you are stuck looking for a command, read doc.txt that has everything, or find the code in one of the test games that does what you need
-if you get really stuck and can't find the answer in doc.txt, ask how to do what you want in here

Creator of PyWright, the lovable case construction system!
Also visit the PyWright post.

Re: The PyWright Casemaker Thread - beta 10.7 (nov30)

Thu Dec 04, 2008 9:58 pm

MrCheeze

Gender: None specified

Rank: Prosecutor

Joined: Fri Sep 05, 2008 9:18 pm

Posts: 821

Crash when clicking the sound tab after changing sound bits:

Code:

Traceback (most recent call last):
  File "PyWright.py", line 4, in <module>
  File "core\libengine.py", line 1510, in run
    assets.cur_script.handle_events(pygame.event.get([pygame.MOUSEMOTION,pygame.MOUSEBUTTONUP,pygame.MOUSEBUTTONDOWN]))
  File "core\libengine.py", line 193, in handle_events
    gui.widget.handle_events(self,n)
  File "core\gui.py", line 103, in handle_events
    self.event("click_down_over",evt.pos)
  File "core\gui.py", line 76, in event
    done = w.event(name,p2,*args)
  File "core\gui.py", line 76, in event
    done = w.event(name,p2,*args)
  File "core\gui.py", line 82, in event
    func(*args)
  File "core\gui.py", line 399, in click_down_over
    getattr(tob,f)()
  File "core\libengine.py", line 1153, in sound
    if t.text==str(int(assets.music_volume)):
  File "core\core.py", line 205, in <lambda>
    music_volume = property(lambda self:pygame.mixer.music.get_volume()*100,smus)
pygame.error: mixer system not initialized

Also no "Objection!" when pressing 4 or 32 bits.

Also by this point the "..." pause after each period should be fixed.

Also switching from 2 screens to 1 during the game or case select makes the game only show the top screen, which is no use. Also the right bg doesn't show for 2-screen case selecting.

Re: The PyWright Casemaker Thread - beta 10.7 (nov30)

Fri Dec 05, 2008 9:34 am

saluk

Gender: Male

Rank: Prosecutor

Joined: Thu Mar 06, 2008 8:36 pm

Posts: 770

Yeah, realtime switching of modes is a bit difficult, but I'll have it sorted out at some point. Probably the same time save/load works again. I need to simplify the core to lessen the workload for these kinds of changes. Soon, but it's not the top of the list.

The reason no objection is heard at 4 bits is because 4 bits isn't supported on your system. In fact, I'm not sure if 4 bits is supported on any system, I have taken 4 and 32 out in beta 10.72. The reason setting the music was crashing was because you set the sound to an invalid format, and then tried to change the volume.

10.72 also puts in the default male and female blips for all official characters, and gives a way to define defaults of your own. And "..." is fixed too.

Creator of PyWright, the lovable case construction system!
Also visit the PyWright post.

Re: The PyWright Casemaker Thread - beta 10.7 (nov30)

Sat Dec 06, 2008 3:47 pm

ProsecutorEdgeworth

Gender: None specified

Rank: Suspect

Joined: Sat Nov 08, 2008 3:09 pm

Posts: 42

Maybe it's just me... :yuusaku:

But,the new version 7.2 fails a bit on the names,isn't it? I mean,for example:

Spoiler:

Instead of displaying "Phoenix"over the text...The text appear without a name!

Re: The PyWright Casemaker Thread - beta 10.7 (nov30)

Sat Dec 06, 2008 5:22 pm

saluk

Gender: Male

Rank: Prosecutor

Joined: Thu Mar 06, 2008 8:36 pm

Posts: 770

Thanks for pointing that out.

To accomplish what you want, this will work:

Code:

char maya
'Hi Nick"
char phoenix hide
"Hi maya"

Creator of PyWright, the lovable case construction system!
Also visit the PyWright post.

Re: The PyWright Casemaker Thread - beta 10.7 (nov30)

Sat Dec 06, 2008 10:42 pm

MrCheeze

Gender: None specified

Rank: Prosecutor

Joined: Fri Sep 05, 2008 9:18 pm

Posts: 821

Wasn't nt dropped ages ago?

Re: The PyWright Casemaker Thread - beta 10.7 (nov30)

Sat Dec 06, 2008 11:36 pm

saluk

Gender: Male

Rank: Prosecutor

Joined: Thu Mar 06, 2008 8:36 pm

Posts: 770

MrCheeze wrote:

Wasn't nt dropped ages ago?

Actually, I thought so too, and was surprised to see a comment on it. But, it's still listed in the doc, and the doc says its for exactly what ProsecutorEdgeworth was using it for. According to the changelog I made this change in 10.2, and haven't done anything to it yet.

I'd just as soon get rid of the command though. It's a relic of the past, when portraits were just another kind of sprite. If no one has any objections I will be removing it at some point. Consider it DEPRECATED.

-------------------------------------------------

I have started a new branch of code so that I can work on simplifying and cleaning up the messy pywright core. Until this is finished (probably beta 11), there will mostly be only simple bugfixes in further beta 10.x releases. I still will take bug reports, but I probably wont take the time to fix anything that has a workaround, until after I finish the new project.

Here are some things the new core should help improve (in other words, no need to report these specific issues until a version is released with the new core that still exhibits these problems):
* dual screen support - switching back and forth, things appearing on the wrong screen, "bleeding" between screens (like the psyche lock which shows the chains crossing onto screen 2)
* random bugs with specific object types (how come char deletes the previous character and a second ev doesn't?)
* confusing issues with object priorities (character stops blinking when something else is displayed)
* being able to choose whether something is displayed on screen 2, screen 1, or "either" depending on what's available
* performance - a simpler core will be easier for me to see where performance problems are
* save/load should make a return

However, the main purpose of the adjustment is for my sanity rather than for my users. It shouldn't affect script syntax at all, this work is about making pywright a better engine and making how it functions a bit more clear. Not that the next major release wont have new syntax, but that will be a separate issue that I'm not looking into at the moment. Beta 10 has been mostly about syntax, such as all of the new power with macros and variables. Beta 11 (or whatever it ends up being) will be more about making the engine a better, less flaky foundation to build on.

No release date, but I'll post updates on my progress.

Creator of PyWright, the lovable case construction system!
Also visit the PyWright post.

Re: The PyWright Casemaker Thread - beta 10.7 (nov30)

Sat Dec 06, 2008 11:41 pm

MrCheeze

Gender: None specified

Rank: Prosecutor

Joined: Fri Sep 05, 2008 9:18 pm

Posts: 821

Maybe you should drop the second screen altogether, it's only going to get more and more complicated with some users using it and some not. I may have said this already, but it was only used for DS because they had to.

Re: The PyWright Casemaker Thread - beta 10.7 (nov30)

Sun Dec 07, 2008 12:15 am

saluk

Gender: Male

Rank: Prosecutor

Joined: Thu Mar 06, 2008 8:36 pm

Posts: 770

I wouldn't mind dropping it, but it's useful in some cases. I do have hopes of eventually porting pywright to the ds (if I ever "finish" the computer version anyway)... Dropping the second screen wouldn't really be good in that case. Also I want to be able to support cases made in other casemakers at some point (or allow cases in pywright to be taken elsewhere), and being too different isn't a benefit when talking about compatibility.

Case-writers will be able to choose whether they want to support the second screen or not. I haven't fully worked out the nature of this, but in general everything an author places on screen2 will be moved to screen1 if screen2 isn't there. There might be cases where screen2 things are optional, and they could be set to not draw. Also, I could make an option for a case to be 2 screen only or 1 screen only, rather than letting the user choose and sacrifice artistic integrity...

But by all means, if you don't like the 2 screens, don't use them.

I only added DS because there were complaints about it missing, but now that it's there I kinda like it.

Creator of PyWright, the lovable case construction system!
Also visit the PyWright post.

Re: The PyWright Casemaker Thread - beta 10.7 (nov30)

Sun Dec 07, 2008 12:47 am

KSA_Tech

AIGE/PWLib Casemaker Developer

Gender: Male

Location: Brazil

Rank: Ace Attorney

Joined: Sun Mar 09, 2008 3:38 am

Posts: 2731

Making the DS effect is something you need to do a solid base on, and think of the effects it might expose, not simply "put it there".
If it's too bugged, delete it and redo it. Sometimes it is better then trying to patch the problems.

The AIGE you see today powering PWLib was something that took a lot of tries to get stable and solid. It was a hard path, but once I got it right, it is nice.

Don't listen to MrCheese: focus on the DS and get it right this time.

:minuki:

PWLib 1.2 Under Development

PWLib Casemaker (Version 1.1) at http://forums.court-records.net/viewtopic.php?f=36&t=8788

Re: The PyWright Casemaker Thread - beta 10.7 (nov30)

Sun Dec 07, 2008 12:59 am

MrCheeze

Gender: None specified

Rank: Prosecutor

Joined: Fri Sep 05, 2008 9:18 pm

Posts: 821

Wait, when was it got wrong in the first place?

Anyway, what IS the second screen good for?

Actually, I guess it would make percieving better since you get a view of the full body. I don't see any other uses though. Well there is the fact that you can look at evidence and testimony at the same time (which was even possible for GBA, but not for DS-style Court Record with a single screen)

Re: The PyWright Casemaker Thread - beta 10.7 (nov30)

Sun Dec 07, 2008 1:10 am

KSA_Tech

AIGE/PWLib Casemaker Developer

Gender: Male

Location: Brazil

Rank: Ace Attorney

Joined: Sun Mar 09, 2008 3:38 am

Posts: 2731

The idea of the dual screen is mostly to make it look as the DS version of the Phoenix Wright games.
I prefer the dual screen over the single one (as I never played GS).

It's a matter of preference.

For speed, saluk should not do DS. For looks, he should do DS.

PWLib supports DS because I made it based on the DS versions.
PyWright supports SS because it was based on the GB versions.

PWLib 1.2 Under Development

PWLib Casemaker (Version 1.1) at http://forums.court-records.net/viewtopic.php?f=36&t=8788

Re: The PyWright Casemaker Thread - beta 10.7 (nov30)

Sun Dec 07, 2008 1:42 am

saluk

Gender: Male

Rank: Prosecutor

Joined: Thu Mar 06, 2008 8:36 pm

Posts: 770

PyWright was NOT based on GB version. PyWright was designed to be single screen from the start because I was making my own Phoenix Wright game for the computer, and I saw no reason to keep the Dual Screen layout on a wide computer screen. Then, users petitioned for the feature, I caved and added it. I made a point not to erase single screen and focus on dual screen, because the number of users who had to have dual screen was low, and there were already people who liked the single screen view.

For this reason, I can't really erase the feature, I have to take into account both types of users and find some kind of balance.

It IS a matter of preference, which is why I must support both.

KSA, I already did DS, it's not perfect but it's 99% fine. Since I am redoing some of the basic building blocks of the engine, it makes sense to rethink DS from that level.

I prefer to "put it there", see if people think a feature is worth the effort after having a test, and then work on perfecting it; as opposed to spending much time to develop something and then finding out no one likes it anyway. Just my style. Your style has value too, but it's not mine. When I am not in beta then there will be a stable version that doesn't change much and tends to "just work" and a beta version where I continue to play with new things.

But this task I am doing is not about DualScreen, it's about something else entirely. It's not even about bugs, its about making my life easier as I go forward. It's just that with the new system, better DS will be very easy for me to do, so I might as well do it.

Creator of PyWright, the lovable case construction system!
Also visit the PyWright post.

Re: The PyWright Casemaker Thread - beta 10.7 (nov30)

Sun Dec 07, 2008 3:05 am

KSA_Tech

AIGE/PWLib Casemaker Developer

Gender: Male

Location: Brazil

Rank: Ace Attorney

Joined: Sun Mar 09, 2008 3:38 am

Posts: 2731

PyWright must be at least loosely based on the GB version due to its single screen build (and to look like Phoenix Wright).

Not depending on your style, just "put it there" is one of the worst approaches you can give to any feature. I had some issues with this way before I realized it was stupid.
Good programmers think the effects of new features and how a certain implementation will affect the system in the future. At first, just putting it there is nice, since you see the thing working, but at some given time, your engine will get bugged, and fixing it will be a pain (I had this issue with previous versions of AIGE), that you will need to redo it.

I see you're redoing some of the engine, thus proving my point. AIGE's core was always the same since PWLib 1.0, and I took my time thinking on the core to not have to redo it after a while. Same goes to PWLib's core.

Sometimes it is better to double your development time at first then to have to work 3 times more to rework something.

:keiko:

PWLib 1.2 Under Development

PWLib Casemaker (Version 1.1) at http://forums.court-records.net/viewtopic.php?f=36&t=8788

Re: The PyWright Casemaker Thread - beta 10.7 (nov30)

Sun Dec 07, 2008 4:23 am

MrCheeze

Gender: None specified

Rank: Prosecutor

Joined: Fri Sep 05, 2008 9:18 pm

Posts: 821

Conclusion: leave it in if you want.

(I think PWLib was originally a cross between GB and DS, according to the wiki?)

Re: The PyWright Casemaker Thread - beta 10.7 (nov30)

Sun Dec 07, 2008 4:41 am

KSA_Tech

AIGE/PWLib Casemaker Developer

Gender: Male

Location: Brazil

Rank: Ace Attorney

Joined: Sun Mar 09, 2008 3:38 am

Posts: 2731

Each programmer, each way.

I never played the GBA version, so PWLib is entirely based on the DS version.

PWLib 1.2 Under Development

PWLib Casemaker (Version 1.1) at http://forums.court-records.net/viewtopic.php?f=36&t=8788

Re: The PyWright Casemaker Thread - beta 10.7 (nov30)

Sun Dec 07, 2008 4:45 am

GolemdX

Argent Sunfly

Gender: None specified

Rank: Suspect

Joined: Thu Nov 27, 2008 9:23 pm

Posts: 47

I found this about Python on DS.
http://mail.python.org/pipermail/python ... 58252.html

I dunno if it will help.

Re: The PyWright Casemaker Thread - beta 10.7 (nov30)

Sun Dec 07, 2008 7:38 am

saluk

Gender: Male

Rank: Prosecutor

Joined: Thu Mar 06, 2008 8:36 pm

Posts: 770

Thanks GolemdX. I also know of lua for ds. Unfortunately, both of those have limitations in how much of the hardware they can utilize. When I am ready to port, I will look at all available options. I expect the best option will be to just code it in c. I have some experience with ds programming. Some things aren't so bad, others can be a bit difficult. I would most likely not write a full wrightscript interpreter, but instead have some sort of compiler. But who knows what I'll think about it when I am actually ready to sit down and begin the project. PyWright pc will have to be more or less stable before it happens.

KSA, don't come into my thread and lecture me on "real programming" or how stupid may way of doing things is. That's extremely rude. I am morphing the engine from one way to a similar but slightly different way. This is what's known as refactoring. The only reason I have an inkling of how the new way might be better, is because I have been working on it the same way for long enough to see what can be fixed. I doubt I would have been able to know the right way to do it if I hadn't started somewhere. I'm not recoding everything from scratch, just refining what's already there. You have had the same system since 1.0 eh? What about before that? PyWright is not at 1.0 yet. Give me a break.

My development time is basically the same as yours. I do half the work first getting things working, then half the work getting things working right. The danger of doing double the work to get it right in the first case, is what if you DONT get it right? Now you have spent twice as long, and still have stuff to redo. If you spend double the time on the rewrite, you have now spent twice as much time as me. What about all of the functions whose arguments you are changing around. You have to change things sometimes too. Why are you criticizing me and saying that me making my code better is a bad thing? Code can ALWAYS be better.

PyWright is not based on the gba version at all, I never played it. PyWright is based on my interpretation of how I thought phoenix wright on pc would look like. Basically, it's based on DS but fitting everything on one screen. There are options for gba mode, but don't tell me what it's based on when I created it.

Stop posting offensive comments here. Please.

Creator of PyWright, the lovable case construction system!
Also visit the PyWright post.

Re: The PyWright Casemaker Thread - beta 10.7 (nov30)

Sun Dec 07, 2008 8:04 am

Neon Lemmy Koopa

Yo Dawg!

Gender: Male

Location: Houston, Texas

Rank: Ace Attorney

Joined: Wed Oct 17, 2007 12:57 am

Posts: 1221

KSA_Tech wrote:

PyWright must be at least loosely based on the GB version due to its single screen build (and to look like Phoenix Wright).

Not depending on your style, just "put it there" is one of the worst approaches you can give to any feature. I had some issues with this way before I realized it was stupid.
Good programmers think the effects of new features and how a certain implementation will affect the system in the future. At first, just putting it there is nice, since you see the thing working, but at some given time, your engine will get bugged, and fixing it will be a pain (I had this issue with previous versions of AIGE), that you will need to redo it.

I see you're redoing some of the engine, thus proving my point. AIGE's core was always the same since PWLib 1.0, and I took my time thinking on the core to not have to redo it after a while. Same goes to PWLib's core.

Sometimes it is better to double your development time at first then to have to work 3 times more to rework something.

:keiko:

KSA I think by "putting it there", Saluk means just putting it in to see what happens and if it will work, and if it does, THEN he works on getting it integrated perfectly into the code. I do that my own self. I think the way you see it as is putting it in and then leaving it there, which is indeed stupid. But I dont think that's what saluk meant (correct me if I'm wrong saluk).

I aint tryin to put you or your casemaker down, KSA. I'm keeping an open mind here, but coming into another's thread and calling their methods unprofessional and then preaching about "Good programming" is ugly, man. People should do what they want to SO LONG as they know what theyre doing, and Saluk seems to know what hes doing.

As far as game styles is concerned, I never understood why people tried to recreate the DS style in casemakers, but I never gave it much thought either. To me, either seems practical so long as they can be figured out with no effort at all.

Re: The PyWright Casemaker Thread - beta 10.7 (nov30)

Sun Dec 07, 2008 12:28 pm

KSA_Tech

AIGE/PWLib Casemaker Developer

Gender: Male

Location: Brazil

Rank: Ace Attorney

Joined: Sun Mar 09, 2008 3:38 am

Posts: 2731

People, just try to read things and understand then at first.
I never said that you're unprofessional, hell. I just mentioned that the worst possible method to add something to a program is just implementing it the first way you think it, without thinking on any consequences. I did that all the time.
This has nothing to do with real programming, just good programming skills. A good programmer is the one who makes a flexible, easy to work code, not one who adds things by random without thinking into the consequences. If you do that, then you should improve your programming tatics. I did it on the past, so I'm not free of it too.
Why do people never read when I say "I did that too" and always get the bad end?

I feel pretty stupid for remaking AIGE the number of times I did, but that was result of I not sitting and thinking patiently.

It's not because a program is not 1.0 or not "beta" that you can "crap it out", saluk. If you're redoing it to make it better because you thought into a better idea, it's ok.

The point I made wasn't that "saluk is crappy on programming because he is reworking pywright", but "adding thing with the first idea you get it stupid". If you didn't do it, there's no reason to cry. Refactoring is fine, I do that all the time. Good programmers do it. That wasn't the point of my previous comment.

I think you got the idea that "refactoring is stupid", but that isn't the point I made there.

I refactored AIGE a bit too.

In the end I think that I mistook saluk's put it there for other thing, and saluk instead of correcting me just yelled like a train without thinking straight. I never had any reason to say saluk is not a decent programmer.

PWLib 1.2 Under Development

PWLib Casemaker (Version 1.1) at http://forums.court-records.net/viewtopic.php?f=36&t=8788

Re: The PyWright Casemaker Thread - beta 10.7 (nov30)

Sun Dec 07, 2008 12:54 pm

ProsecutorEdgeworth

Gender: None specified

Rank: Suspect

Joined: Sat Nov 08, 2008 3:09 pm

Posts: 42

Well...Maybe I didn't come on the best time?
KSA,I agree with saluk that going into another person' post to criticise it,it's not very polite...
Anyway,PyWright is faster than before,isn't it?
(If you try Gant's emotion;he doesn't stop with his hair!)

Re: The PyWright Casemaker Thread - beta 10.7 (nov30)

Sun Dec 07, 2008 1:06 pm

KSA_Tech

AIGE/PWLib Casemaker Developer

Gender: Male

Location: Brazil

Rank: Ace Attorney

Joined: Sun Mar 09, 2008 3:38 am

Posts: 2731

Oh, so i can't criticize now?
Ok, noted: saluk doesn't like criticism.

Anyway, if what I said isn't what HE did, then there wasn't no reason to yell anything.
If he did, she SHOULD take the advice and make himself a better programmer.
I learned that criticism is a good thing, by all means. If he can't take it, I won't say anything else.

PWLib 1.2 Under Development

PWLib Casemaker (Version 1.1) at http://forums.court-records.net/viewtopic.php?f=36&t=8788

Re: The PyWright Casemaker Thread - beta 10.7 (nov30)

Sun Dec 07, 2008 2:31 pm

MrCheeze

Gender: None specified

Rank: Prosecutor

Joined: Fri Sep 05, 2008 9:18 pm

Posts: 821

Those were ProsecutorEdgeworth's words, not saluk's.

But anyway, I think he was talking about how you were so insistant that your way was the "right" way? I agree with you partly (since the dual screen is a result of "putting it there", and I see how problems can come from that), but I still agreed in the end that if that's the way he wants to do it, that's the way he can.

Re: The PyWright Casemaker Thread - beta 10.7 (nov30)

Sun Dec 07, 2008 3:15 pm

KSA_Tech

AIGE/PWLib Casemaker Developer

Gender: Male

Location: Brazil

Rank: Ace Attorney

Joined: Sun Mar 09, 2008 3:38 am

Posts: 2731

I think that I misinterpret the "putting it there" that saluk said. If that's the case, he shouldn't freak out and tell me I pointed the wrong thing, so it wouldn't have any problem.

Just rushing and implementing the first idea you have is not a good option (but valid in the end). << that was the point i made
Implementing it partially to see the results is totally different.

So, saluk, next time before screaming out, let me know if I misinterpret your idea. It avoids issues.
I had no intention of attacking, I know it doesn't work to any good, and I have no reason to do so too.

PWLib 1.2 Under Development

PWLib Casemaker (Version 1.1) at http://forums.court-records.net/viewtopic.php?f=36&t=8788

Re: The PyWright Casemaker Thread - beta 10.7 (nov30)

Sun Dec 07, 2008 5:34 pm

saluk

Gender: Male

Rank: Prosecutor

Joined: Thu Mar 06, 2008 8:36 pm

Posts: 770

KSA you are the one who mentioned "putting it there" in the first place. Maybe you weren't insinuating that's what I do, but it sure seemed like that. I don't mind criticism of my results, but I do mind criticism of myself or my techniques, which is how your posts sound. Especially since you chose my little announcement as a perfect time to say something that sounded to me like, "hmm, need to rewrite your bad code now saluk, hehe." Advice is one thing, lectures are another. In text it's hard to tell the difference, but your posts come off sounding like trolling rather than anything else. And sounding bad is almost as bad as if you meant them that way.

I don't think I spouted off like a train either. I had rebuttals for your points. My last line was harsh, but I am tired of feeling like I have to defend myself to you constantly.

You are right about implementing the first idea with no thought. Not only is that silly, but I don't see how it's even possible. With a big complex system as PyWright or AIGE is, there has to be a little bit of making sure what you put will even work, let alone make sense.

Just to clarify, I do a little bit of planning/thinking to see how something might work, start programming it that way, and if it seems to be the right track I complete it.

ProsecutorEdgeworth, there is no bad time to visit my thread :will:

Yes, I did make some fixes to speed things up in the last version, although it wasn't enough for poor MrCheeze :payne:

MrCheeze: maybe I should make a poll about dual screen, I dunno. When I planned to add it there were a lot of people complaining about dual screen not being there. However, I think most of those people have gone to pwlib now anyway. I also have to consider whether new users might prefer it. In any case it will never be required.

Creator of PyWright, the lovable case construction system!
Also visit the PyWright post.

Re: The PyWright Casemaker Thread - beta 10.7 (nov30)

Sun Dec 07, 2008 6:04 pm

KSA_Tech

AIGE/PWLib Casemaker Developer

Gender: Male

Location: Brazil

Rank: Ace Attorney

Joined: Sun Mar 09, 2008 3:38 am

Posts: 2731

I wasn't insulting what you do.
Now that it's sorted, let's move on.

I think you should do what you think it's better for you. Don't do DS only if your users want it, but do it because you feel up to do it. That's my opinion.

PWLib 1.2 Under Development

PWLib Casemaker (Version 1.1) at http://forums.court-records.net/viewtopic.php?f=36&t=8788

Re: The PyWright Casemaker Thread - beta 10.7 (nov30)

Sun Dec 07, 2008 6:57 pm

saluk

Gender: Male

Rank: Prosecutor

Joined: Thu Mar 06, 2008 8:36 pm

Posts: 770

Well, since DS is already in, and it basically works fine, the discussion is more whether the feature should be removed. It's not a matter of whether I can do it or not, but what people want. If I was doing the project for me alone, I probably would drop dual screen because I have no need of it, but the project has stopped being just for me a long time ago. The reason I think I shouldn't drop it, is because it will be hard to add back in later, so I want to have it for future.

I'll post again when I have made progress.

Creator of PyWright, the lovable case construction system!
Also visit the PyWright post.

Re: The PyWright Casemaker Thread - beta 10.7 (nov30)

Sun Dec 07, 2008 7:20 pm

MrCheeze

Gender: None specified

Rank: Prosecutor

Joined: Fri Sep 05, 2008 9:18 pm

Posts: 821

Unrelated bug: Can no longer load emotions that aren't separated into talk/blink/combined.

Re: The PyWright Casemaker Thread - beta 10.7 (nov30)

Sun Dec 07, 2008 8:30 pm

saluk

Gender: Male

Rank: Prosecutor

Joined: Thu Mar 06, 2008 8:36 pm

Posts: 770

Fixed in 10.74. Interesting to note that the bug was caused by just a couple missing characters. If you update with the auto-update (from pywright exe), it may crash at first. Just run it again and it should work again - this is a bug with autoupdate. I also added a feature for pywright to download missing characters before running a game. Since characters can be a bit big, I'll probably move this out of the main engine and into the updater so it happens when you download the game instead of play it.

Creator of PyWright, the lovable case construction system!
Also visit the PyWright post.

Re: The PyWright Casemaker Thread - beta 10.7 (nov30)

Mon Dec 08, 2008 12:50 am

yoshirider4

Gender: None specified

Rank: Suspect

Joined: Thu Nov 27, 2008 12:59 am

Posts: 39

Ok, I found out how to import my guy, he's a .gif. When I put him in the game, the blinking pose wouldn't animate and the talk pose wouldn't animate and it screwed up his colors. :payne:

...Does anyone know what I did wrong?

Code:

bg black
char leck
"{ehappy(talk)}randomtext."
"I wanna test this out, now"

Me Sprites!?

Re: The PyWright Casemaker Thread - beta 10.7 (nov30)

Mon Dec 08, 2008 1:01 am

saluk

Gender: Male

Rank: Prosecutor

Joined: Thu Mar 06, 2008 8:36 pm

Posts: 770

The talk and blink are automatically set by the text printer. It sets to talk when letters are displayed, and sets to blink for any text inside parenthesis or when the text is finished printing. Just call the emotion without the (talk) or (blink) part:

Code:

bg black
char leck
"{ehappy}randomtext."
"I wanna test this out, now"

Creator of PyWright, the lovable case construction system!
Also visit the PyWright post.

Re: The PyWright Casemaker Thread - beta 10.7 (nov30)

Mon Dec 08, 2008 1:06 am

yoshirider4

Gender: None specified

Rank: Suspect

Joined: Thu Nov 27, 2008 12:59 am

Posts: 39

Well the talk and blink animations are separated, and I named them happy(talk) and happy(blink) so without it in the code it came out as an error...

Me Sprites!?

Re: The PyWright Casemaker Thread - beta 10.7 (nov30)

Mon Dec 08, 2008 1:13 am

saluk

Gender: Male

Rank: Prosecutor

Joined: Thu Mar 06, 2008 8:36 pm

Posts: 770

Are happy(talk).gif and happy(blink).gif located in art/port/leck?

That can be pywright/art/port/leck, or pywright/games/yoshirider4_game/art/port/leck.

The code should look like the code I posted. If it's still not working there could be a problem with one of the gifs. Try {ehappy(blink)} and see if you get the error.

There may be a bug report in here somewhere but I don't have much information to go on. If you can't get it to work, try sending me the gif files and I'll test it here.

Creator of PyWright, the lovable case construction system!
Also visit the PyWright post.

Re: The PyWright Casemaker Thread - beta 10.7 (nov30)

Mon Dec 08, 2008 1:20 am

yoshirider4

Gender: None specified

Rank: Suspect

Joined: Thu Nov 27, 2008 12:59 am

Posts: 39

Alright, something is wrong here. Here's the animations.

happy(blink)

happy(talk)

Me Sprites!?

Re: The PyWright Casemaker Thread - beta 10.7 (nov30)

Mon Dec 08, 2008 1:56 am

saluk

Gender: Male

Rank: Prosecutor

Joined: Thu Mar 06, 2008 8:36 pm

Posts: 770

There are 2 problems, one on your end and one in pywright itself. First, the gif format only supports 8 bit indexed images. Whatever program you used is a bit less strict about the format. That accounts for the weird colors you were seeing. So you need to convert it to 8bit(256 colors).

The animation problem is because the gif reader is using outdated settings commands. Here's my edits to the image settings files that fixes animation:

happy(blink).txt

Code:

length 1
loops 1

happy(talk).txt

Code:

length 4
loops 1

As it's a bug that only shows up with new gif files, and I haven't added any new gif files for a while, I didn't catch it.

Creator of PyWright, the lovable case construction system!
Also visit the PyWright post.

Last edited by saluk on Mon Dec 08, 2008 7:32 am, edited 1 time in total.

Re: The PyWright Casemaker Thread - beta 10.7 (nov30)

Mon Dec 08, 2008 3:18 am

GolemdX

Argent Sunfly

Gender: None specified

Rank: Suspect

Joined: Thu Nov 27, 2008 9:23 pm

Posts: 47

Change it so game names with invalid folder characters can't be created.

Re: The PyWright Casemaker Thread - beta 10.7 (nov30)

Mon Dec 08, 2008 8:03 am

saluk

Gender: Male

Rank: Prosecutor

Joined: Thu Mar 06, 2008 8:36 pm

Posts: 770

If you mean in the editor "create game" option, this is now fixed in the latest release. The invalid default settings for gifs discussed above are fixed now as well.

Creator of PyWright, the lovable case construction system!
Also visit the PyWright post.

Re: The PyWright Casemaker Thread - beta 10.7 (nov30)

Mon Dec 08, 2008 1:25 pm

GolemdX

Argent Sunfly

Gender: None specified

Rank: Suspect

Joined: Thu Nov 27, 2008 9:23 pm

Posts: 47

I did mean that. Also, the back button for evidence on dualscreen doesn't seem to be working. I opened it on the default text.