- May 24, 2017
- 1,456
- 2,108
I believe this is what I did for #2Ok so the game has changed a lot but here is a few issues that I have wit the new version
2.) Boy with dog bite there is no way to get around loosing a point with it now it seems. You do all the exam and the only thing left is abdomen but there is no way to skip it you are forced to fondle the boy in a sense oO
[code]
I'm sorry, but an uncaught exception occurred.
While running game code:
File "game/main.rpy", line 1309, in script call
call events_run_period from _call_events_run_period
File "game/event_dispatcher.rpy", line 297, in script call
call expression _event from call_expression_event_1
File "game/main.rpy", line 1309, in script call
call events_run_period from _call_events_run_period
File "game/event_dispatcher.rpy", line 297, in script call
call expression _event from call_expression_event_1
File "game/main.rpy", line 1309, in script call
call events_run_period from _call_events_run_period
File "game/event_dispatcher.rpy", line 297, in script call
call expression _event from call_expression_event_1
File "game/main.rpy", line 1331, in script call
call events_run_period from _call_events_run_period_1
File "game/event_dispatcher.rpy", line 297, in script call
call expression _event from call_expression_event_1
File "game/main.rpy", line 1345, in script call
call events_run_period from _call_events_run_period_2
File "game/event_dispatcher.rpy", line 297, in script call
call expression _event from call_expression_event_1
File "game/main.rpy", line 1331, in script call
call events_run_period from _call_events_run_period_1
File "game/event_dispatcher.rpy", line 297, in script call
call expression _event from call_expression_event_1
File "game/main.rpy", line 1309, in script call
call events_run_period from _call_events_run_period
File "game/event_dispatcher.rpy", line 297, in script call
call expression _event from call_expression_event_1
File "game/main.rpy", line 1345, in script call
call events_run_period from _call_events_run_period_2
File "game/event_dispatcher.rpy", line 297, in script call
call expression _event from call_expression_event_1
File "game/main.rpy", line 1309, in script call
call events_run_period from _call_events_run_period
File "game/event_dispatcher.rpy", line 297, in script call
call expression _event from call_expression_event_1
File "game/main.rpy", line 1199, in script call
call calendar(1) from _call_calendar
File "game/calendar.rpy", line 148, in script
if displayYear:
File "game/calendar.rpy", line 148, in <module>
if displayYear:
NameError: name 'displayYear' is not defined
-- Full Traceback ------------------------------------------------------------
Full traceback:
File "game/main.rpy", line 1309, in script call
call events_run_period from _call_events_run_period
File "game/event_dispatcher.rpy", line 297, in script call
call expression _event from call_expression_event_1
File "game/main.rpy", line 1309, in script call
call events_run_period from _call_events_run_period
File "game/event_dispatcher.rpy", line 297, in script call
call expression _event from call_expression_event_1
File "game/main.rpy", line 1309, in script call
call events_run_period from _call_events_run_period
File "game/event_dispatcher.rpy", line 297, in script call
call expression _event from call_expression_event_1
File "game/main.rpy", line 1331, in script call
call events_run_period from _call_events_run_period_1
File "game/event_dispatcher.rpy", line 297, in script call
call expression _event from call_expression_event_1
File "game/main.rpy", line 1345, in script call
call events_run_period from _call_events_run_period_2
File "game/event_dispatcher.rpy", line 297, in script call
call expression _event from call_expression_event_1
File "game/main.rpy", line 1331, in script call
call events_run_period from _call_events_run_period_1
File "game/event_dispatcher.rpy", line 297, in script call
call expression _event from call_expression_event_1
File "game/main.rpy", line 1309, in script call
call events_run_period from _call_events_run_period
File "game/event_dispatcher.rpy", line 297, in script call
call expression _event from call_expression_event_1
File "game/main.rpy", line 1345, in script call
call events_run_period from _call_events_run_period_2
File "game/event_dispatcher.rpy", line 297, in script call
call expression _event from call_expression_event_1
File "game/main.rpy", line 1309, in script call
call events_run_period from _call_events_run_period
File "game/event_dispatcher.rpy", line 297, in script call
call expression _event from call_expression_event_1
File "game/main.rpy", line 1199, in script call
call calendar(1) from _call_calendar
File "game/calendar.rpy", line 148, in script
if displayYear:
File "C:\Users\oguzh\Desktop\General_Practitioner-005b-pc-4b94a679GCjHq\General_Practitioner-0.0.5b-pc\renpy\ast.py", line 1656, in execute
if renpy.python.py_eval(condition):
File "C:\Users\oguzh\Desktop\General_Practitioner-005b-pc-4b94a679GCjHq\General_Practitioner-0.0.5b-pc\renpy\python.py", line 1749, in py_eval
return py_eval_bytecode(code, globals, locals)
File "C:\Users\oguzh\Desktop\General_Practitioner-005b-pc-4b94a679GCjHq\General_Practitioner-0.0.5b-pc\renpy\python.py", line 1743, in py_eval_bytecode
return eval(bytecode, globals, locals)
File "game/calendar.rpy", line 148, in <module>
if displayYear:
NameError: name 'displayYear' is not defined
Windows-8-6.2.9200
Ren'Py 6.99.12.4.2187
General Practitioner 0.0.5
This kind of error usually comes when you load a savegame after an update without starting a new game. With each update you'll need to start a new game, whether from scratch or skipping to the update.@Bruni Multimedia i get this error, its after i accept/decline the job offer from Dr.Richards
Code:[code] I'm sorry, but an uncaught exception occurred. While running game code: File "game/main.rpy", line 1309, in script call call events_run_period from _call_events_run_period File "game/event_dispatcher.rpy", line 297, in script call call expression _event from call_expression_event_1 File "game/main.rpy", line 1309, in script call call events_run_period from _call_events_run_period File "game/event_dispatcher.rpy", line 297, in script call call expression _event from call_expression_event_1 File "game/main.rpy", line 1309, in script call call events_run_period from _call_events_run_period File "game/event_dispatcher.rpy", line 297, in script call call expression _event from call_expression_event_1 File "game/main.rpy", line 1331, in script call call events_run_period from _call_events_run_period_1 File "game/event_dispatcher.rpy", line 297, in script call call expression _event from call_expression_event_1 File "game/main.rpy", line 1345, in script call call events_run_period from _call_events_run_period_2 File "game/event_dispatcher.rpy", line 297, in script call call expression _event from call_expression_event_1 File "game/main.rpy", line 1331, in script call call events_run_period from _call_events_run_period_1 File "game/event_dispatcher.rpy", line 297, in script call call expression _event from call_expression_event_1 File "game/main.rpy", line 1309, in script call call events_run_period from _call_events_run_period File "game/event_dispatcher.rpy", line 297, in script call call expression _event from call_expression_event_1 File "game/main.rpy", line 1345, in script call call events_run_period from _call_events_run_period_2 File "game/event_dispatcher.rpy", line 297, in script call call expression _event from call_expression_event_1 File "game/main.rpy", line 1309, in script call call events_run_period from _call_events_run_period File "game/event_dispatcher.rpy", line 297, in script call call expression _event from call_expression_event_1 File "game/main.rpy", line 1199, in script call call calendar(1) from _call_calendar File "game/calendar.rpy", line 148, in script if displayYear: File "game/calendar.rpy", line 148, in <module> if displayYear: NameError: name 'displayYear' is not defined -- Full Traceback ------------------------------------------------------------ Full traceback: File "game/main.rpy", line 1309, in script call call events_run_period from _call_events_run_period File "game/event_dispatcher.rpy", line 297, in script call call expression _event from call_expression_event_1 File "game/main.rpy", line 1309, in script call call events_run_period from _call_events_run_period File "game/event_dispatcher.rpy", line 297, in script call call expression _event from call_expression_event_1 File "game/main.rpy", line 1309, in script call call events_run_period from _call_events_run_period File "game/event_dispatcher.rpy", line 297, in script call call expression _event from call_expression_event_1 File "game/main.rpy", line 1331, in script call call events_run_period from _call_events_run_period_1 File "game/event_dispatcher.rpy", line 297, in script call call expression _event from call_expression_event_1 File "game/main.rpy", line 1345, in script call call events_run_period from _call_events_run_period_2 File "game/event_dispatcher.rpy", line 297, in script call call expression _event from call_expression_event_1 File "game/main.rpy", line 1331, in script call call events_run_period from _call_events_run_period_1 File "game/event_dispatcher.rpy", line 297, in script call call expression _event from call_expression_event_1 File "game/main.rpy", line 1309, in script call call events_run_period from _call_events_run_period File "game/event_dispatcher.rpy", line 297, in script call call expression _event from call_expression_event_1 File "game/main.rpy", line 1345, in script call call events_run_period from _call_events_run_period_2 File "game/event_dispatcher.rpy", line 297, in script call call expression _event from call_expression_event_1 File "game/main.rpy", line 1309, in script call call events_run_period from _call_events_run_period File "game/event_dispatcher.rpy", line 297, in script call call expression _event from call_expression_event_1 File "game/main.rpy", line 1199, in script call call calendar(1) from _call_calendar File "game/calendar.rpy", line 148, in script if displayYear: File "C:\Users\oguzh\Desktop\General_Practitioner-005b-pc-4b94a679GCjHq\General_Practitioner-0.0.5b-pc\renpy\ast.py", line 1656, in execute if renpy.python.py_eval(condition): File "C:\Users\oguzh\Desktop\General_Practitioner-005b-pc-4b94a679GCjHq\General_Practitioner-0.0.5b-pc\renpy\python.py", line 1749, in py_eval return py_eval_bytecode(code, globals, locals) File "C:\Users\oguzh\Desktop\General_Practitioner-005b-pc-4b94a679GCjHq\General_Practitioner-0.0.5b-pc\renpy\python.py", line 1743, in py_eval_bytecode return eval(bytecode, globals, locals) File "game/calendar.rpy", line 148, in <module> if displayYear: NameError: name 'displayYear' is not defined Windows-8-6.2.9200 Ren'Py 6.99.12.4.2187 General Practitioner 0.0.5
I don't follow you, sorry. Can you explain it?I would make the suggestion to stay away from the glowing/sparkling star (*) like is often used in alot of the LoP games. It can be hard to see for some, me in that by the way, and possibly later put that when the mouse cursor is near the area a glove or spyglass is shown as an indicator basically the pointer changes to a visible degree
I don't follow you, sorry. Can you explain it?
Sorry was referring to the above picture and post, about the new/upcoming exam set up. I feel that it would add a new level to the game that would seem a bit more real on the medical side but I was suggesting that in future to consider a sort of hint when the person gets close to the area they are to check, take the picture you provided of the exam that has the gloves and magnifying glass and gloves icons indicate where to look I was meaning to possibly have the icon of a magnifying glass or maybe an eye come up that it was a hotspot to look at where some games use a sparkling star to indicate hidden spots. I am not a fan of the sparkles as I often can not see them. Basically the mouse pointer on screen could change shape when they get over the region to indicate a point of intrest
It was VERY ugly, albeit practical, to indicate which body parts to examine by a text option, I'm well aware of that.
That's why, starting with 0.0.6's "Ice Dream" update all examination will have a clickable hotspot to choose what to examine. A tooltip at the top of the screen will highlight which exam is linked to the body part and for the exams that involve the whole body (or a specific or hidden part) icons will be available on the screen's top right section.
The magnifying lenses will indicate a visual exam, while the glove will indicate a manual exam (either by palpation or percussion). More icons will be added for more specific exams too (i.e. x-rays).
"Ice Dream" will be available in September, so stay in touch.
You must be registered to see the links
Also one thing I'd like to see is more renders for the previous patients, like if you do a test that isn't exactly necessary that it shows the render for that as well.Oh bruni one thing, go through the exam files one of the new girls I think it's the asian one has a bunch of errors there. they don't trigger since it's poorly coded (sorry). The file is filled with "vanilla" code which seems fine, but when using a compare function you've wrote "true" but it should be "True".
Sorry if I'm not clear, I kinda forgot and deleted the files yesterday
Thanks.Oh bruni one thing, go through the exam files one of the new girls I think it's the asian one has a bunch of errors there. they don't trigger since it's poorly coded (sorry). The file is filled with "vanilla" code which seems fine, but when using a compare function you've wrote "true" but it should be "True".
Sorry if I'm not clear, I kinda forgot and deleted the files yesterday
You used the fix in the op right?I haven't read through the whole thread, so maybe this was mentioned, but I'm having trouble shopping. I was able to shop one time and got the advanced medical bed, but now when I try to go back to it, it just skips the evening. Am I missing something obvious?
A couple more bugs that may have already been reported...I got some missing images during the motorcycle accident patient. Looks like Monique_1_Exam_6 is the problem there.
And during the dog bite examination, when using the "calm" option to the mother being upset about asking questions, I get this error.
You don't have permission to view the spoiler content. Log in or register now.
They will come in time. As you are surely well aware rendering is the most time-consuming process of the entire development, and the only thing I can't do while away for work in lunch break (because my computer at work hasn't got a decent video card mostly).Also one thing I'd like to see is more renders for the previous patients, like if you do a test that isn't exactly necessary that it shows the render for that as well.