Osculator file:
I start off in Osculator with creating a manual message "/ya/1" with an OSC Routing of localhost:9000.

PD file:

• receiving code

(object) udpreceive 9000
|
|
(object) unpackOSC
|
|
(object) routeOSC /ya
|
|
(object) routeOSC /1
|
|
(number)
|
|
(object) send hot

• sending code (separated from my receiving code)

(message) connect localhost 9000
|
|
(object) udpsend

(message) disconnect
|
|
(object) udpsend

(object) receive hot
|
|
(message) send /ba/1 $1
|
|
(object) packOSC
|
|
(object) udpsend

...So when i test the /ya/1 message in Osculator with my mouse, I get the /ba/1 message added to Osculator. As I continue to click with my mouse, both of their activity boxes light up green in unison.

I'd like to know if this coding between Oscualtor and PD is efficient enough to move on with practices and tutorials in PD?
Is there a way to code udpreceive and udpsend interconnected rather than separated as seen in my PD file?
Should Osculator have two messages that are OSC Routing rather than one?

Let me know if anything is confusing or in need of clarification. Thanks!

http://www.pdpatchrepo.info/hurleur/sp1.oscd

Your ASCII art, however, could use some work. You should probably take a look at this sticky on the Technical Issues forum

http://puredata.hurleur.com/sujet-6377-read-new-here-understanding-ascii-art-patches

I haven't changed a thing, and now when I open my files and click on the signal to trigger Pure Data from OSC, I get the error "udpsend: not connected". I am very confused to why things could change like that, even after not doing anything. Could anyone suggest possible issues that may be causing this to happen?